Method and apparatus for transmitting synchronization signal for device to device communication in wireless communication system

ABSTRACT

Exemplary embodiments provide a method and apparatus for transmitting a synchronization signal for Device-to-Device (D2D) communication in a wireless communication system. With respect to a D2D synchronization source to transmit a synchronization signal for D2D communication, the method includes: generating a D2D Synchronization Signal (D2DSS); and transmitting, by a synchronization source, the D2DSS to a D2D reception (Rx) UE, wherein the D2DSS includes a Primary D2D Synchronization Signal (PD2DSS) generated based on information associated with the synchronization source.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of a U.S. patent application Ser. No.15/664,415, filed on Jul. 31, 2017, which is a continuation of a U.S.patent application Ser. No. 15/417,677, filed on Jan. 27, 2017, nowissued as U.S. Pat. No. 9,756,588, which is a continuation of a U.S.patent application Ser. No. 14/685,467, filed on Apr. 13, 2015, nowissued as U.S. Pat. No. 9,596,668, which claims priority from and thebenefit of U.S. Provisional Application No. 61/979,003, filed on Apr.14, 2014, and Korean Patent Application No. 10-2014-0103977, filed onAug. 11, 2014, which are incorporated herein by reference in theirentirety.

BACKGROUND

1. Field

Exemplary embodiments relate to wireless communication, and moreparticularly, to a method and apparatus for transmitting asynchronization signal for Device to Device (D2D) communication in awireless communication system.

2. Discussion of the Background

Device to Device (D2D) communication refers to a communication schemethat executes direct data transmission and reception between neighboringtwo User Equipments (UEs) without an evolved NodeB (eNodeB). That is,two UEs act as a source and a destination of data, and executecommunication.

The D2D communication may be executed through a communication schemethat uses a non-licensed band such as a Wireless Local Area Network(LAN), Bluetooth, or the like. However, the communication scheme usingthe non-licensed band may have difficulty in providing planed andcontrolled services. In particular, the performance may be significantlydeteriorated by interference.

Conversely, D2D communication that is operated or provided in alicensed-band or in an environment where inter-system interference iscontrolled, may support Quality of service (QoS) and may increasefrequency utilization efficiency through frequency reusing and mayincrease a communication distance.

In the D2D communication in the licensed band, that is, in the cellularcommunication based-D2D communication, an eNodeB allocates resources ofa UE, and the allocated resources may use a cellular uplink channel.

The D2D communication may include intra-cell D2D communication andinter-cell D2D communication. The inter-cell D2D communication may beembodied based on cooperative communication between two eNodeBs.

Therefore, there is desire for a method for effective use of resourcesand allocating a synchronization signal, for D2D communication servicesin the recent wireless communication system.

SUMMARY

One or more exemplary embodiments provide a method and apparatus fortransmitting a synchronization signal for Device to Device (D2D)communication in a wireless communication system.

One or more exemplary embodiments provide a method and apparatus forconfiguring a synchronization signal in a wireless communication systemthat supports D2D communication.

One or more exemplary embodiments provide a method and apparatus forconfiguring a sequence of a synchronization signal that has goodcorrelation.

One or more exemplary embodiments provide a method of transceiving asynchronization signal by a user equipment (UE) supporting adevice-to-device (D2D) communication between UEs, the method including:receiving, at a first UE, a synchronization signal transmitted from asynchronization source; determining a root index based on the receivedsynchronization signal; determining a synchronization timing referencebased on the root index; and transmitting a synchronization signal for aD2D communication based on the determined synchronization timingreference. The determining of the synchronization timing referenceincludes: based on the root index, determining a category of thesynchronization source; prioritizing the synchronization source based ondetermining whether the synchronization source is an evolved NodeB(eNodeB), a UE synchronized with an eNodeB, or a UE having asynchronization timing reference independent from an eNodeB; anddetermining the synchronization timing reference based on theprioritization. One or more exemplary embodiments provide a method oftransceiving a synchronization signal by a user equipment (UE)supporting a device-to-device (D2D) communication between UEs, themethod including: receiving, at a UE, synchronization signalstransmitted from different synchronization sources, respectively;prioritizing the different synchronization sources based on categoriesof the different synchronization sources, the categories including anevolved NodeB (eNodeB), a UE synchronized with an eNodeB, and a UEhaving a synchronization timing reference independent from an eNodeB;determining a reference synchronization source for the UE among thedifferent synchronization sources; synchronizing with the referencesynchronization source based on a synchronization timing referenceassociated with the reference synchronization source; and transmitting,from the UE, a signal based on the synchronization.

One or more exemplary embodiments provide a method of transceiving asynchronization signal by a user equipment (UE) supporting adevice-to-device (D2D) communication between UEs, the method including:receiving, at a UE, synchronization signals transmitted from differentsynchronization sources, respectively; prioritizing the differentsynchronization sources based on the received synchronization signals;determining a reference synchronization source for the UE among thedifferent synchronization sources; synchronizing with the referencesynchronization source based on a synchronization timing referenceassociated with the reference synchronization source; and transmitting,from the UE, a signal to the reference synchronization source based onthe synchronization. The determining of the reference synchronizationsource includes: determining a root index based on each synchronizationsignal received from the respective synchronization source; determininga category of the respective synchronization source based on the rootindex; prioritizing the different synchronization sources based on thecorresponding categories; and determining the reference synchronizationsource based on the prioritization.

According to one or more exemplary embodiments, D2D synchronizationinformation may be efficiently indicated based on an apparatus thattransmits or receives a D2D signal. Therefore, D2D scheduling allocation(SA) and data information may be efficiently transmitted by securingefficiency of obtaining synchronization between User Equipments (UEs)inside or outside network coverage.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating a concept of cellular network-basedDevice-to-Device (D2D) communication.

FIG. 2 is a conceptual diagram of a system to which a method oftransmitting a synchronization signal is applied according to one ormore exemplary embodiments.

FIG. 3 is a conceptual diagram of a system to which a method oftransmitting a synchronization signal is applied according to one ormore exemplary embodiments.

FIG. 4 is a conceptual diagram of a system to which a method oftransmitting a synchronization signal is applied according to one ormore exemplary embodiments.

FIG. 5 is a block diagram illustrating a wireless communication systemaccording to one or more exemplary embodiments.

FIG. 6 is a flowchart illustrating an example of a method in which a D2Dreception (Rx) UE selects a D2D transmission mode based on a root indexvalue of a received PD2DSS according to one or more exemplaryembodiments.

DETAILED DESCRIPTION OF THE ILLUSTRATED EMBODIMENTS

Hereinafter, exemplary embodiments of the present invention will bedescribed with reference to the accompanying drawings. In the followingdescription, the same elements will be designated by the same referencenumerals although they are shown in different drawings. Further, in thefollowing description, a detailed description of known functions andconfigurations incorporated herein will be omitted when it may make thesubject matter of the present invention rather unclear.

The present specification provides descriptions in association with acommunication network, and tasks executed in the communication networkmay be performed in the process where a system (for example, an evolvedNodeB (eNodeB)) that manages the corresponding communication networkcontrols a network and transmits data, or may be performed in a UserEquipment (UE) that is linked to the corresponding network.

FIG. 1 is a diagram illustrating a concept of cellular network-basedDevice-to-Device (D2D) communication according to one or more exemplaryembodiments.

Referring to FIG. 1, the communication between a first UE 110 located ina first cell and a second UE 120 located in a second cell may be D2Dcommunication between a UE included in a network coverage and a UEincluded in the network coverage. In addition, the communication betweena third UE 130 located in the first cell and a forth UE 140 located in afirst cluster may be D2D communication between a UE included in anetwork coverage and a UE located outside the network coverage. Thecommunication between the fourth UE 140 located in the first cluster anda fifth UE 150 located in the first cluster may be D2D communicationbetween two UEs located outside the network coverage.

D2D communication refers to a technology that enables directtransmission and reception of data between UEs. Hereinafter, a UEdescribed in exemplary embodiments is assumed to support D2Dcommunication. When UEs located close to a cellular system execute D2Dcommunication, loads on an evolved NodeB (eNodeB) may be dispersed. Inaddition, when UEs execute D2D communication, a UE executes datatransmission with respect to a relatively short distance, and thus,transmission power consumption and transmission latency of the UE maydecrease. In addition, from the perspective of the whole system, theexisting cellular-based communication and the D2D communication useidentical resources and thus, frequency utilization efficiency may beimproved.

The D2D communication may be classified into a communication method of aUE located in a network coverage (base station coverage) and acommunication method of a UE located outside a network coverage (basestation coverage). The D2D communication may include a discovery processthat executes discovery for communication between UEs and a directcommunication process in which UEs transmits and receives control dataand/or traffic data. The D2D communication may be used for variouspurposes. For example, D2D in a network coverage may be used for publicsafety and non-public safety such as commercial purposes or the like.The D2D communication executed outside a network coverage may be usedfor only the public safety.

A D2D synchronization source may indicate a node that transmits at leasta D2D synchronization signal (D2DSS). The D2D synchronization source maytransmit at least one D2DSS. The transmitted D2DSS may be used by a UEto obtain time-frequency synchronization. When the D2D synchronizationsource is an eNodeB, a D2DSS transmitted by the D2D synchronizationsource may include a Synchronization Signal (SS) identical to a PrimarySynchronization Signal (PSS) and a Secondary Synchronization Signal(SSS). A D2DSS transmitted by a D2D synchronization source which isdifferent from an eNodeB, may include a signal described in thisdisclosure. For example, when a D2D synchronization source is a UE, abroadcasting UE, a cluster head, a synchronization head, or the like, aD2DSS which is modified from a PSS (hereinafter referred to as a PD2DSS)or a D2DSS that is modified from an SSS (hereinafter referred to as anSD2DSS) may include a signal described in this disclosure. The clusterheader may include an Independent Synchronization Source (ISS) forsynchronization of an out-of-coverage UE, or may operate as an ISS.

A D2DSS transmitted by the D2D synchronization source may include anidentity (ID) of the D2D synchronization source and/or a type of a D2Dsynchronization source. In addition, the D2DSS may include at least aPrimary Device to Device Synchronization Signal (PD2DSS) and a SecondaryDevice to Device Synchronization Signal (SD2DSS). The PD2DSS is based ona Zadoff Chu sequence.

A sequence d(n) used for the PSS may be generated from a frequencydomain Zadoff Chu sequence based on Equation 1.

$\begin{matrix}{{d_{u}(n)} = \left\{ \begin{matrix}e^{{- j}\;\frac{\pi\;{{un}{({n + 1})}}}{63}} & {{n = 0},1,\ldots\mspace{14mu},30} \\e^{{- j}\;\frac{\pi\;{u{({n + 1})}}{({n + 2})}}{63}} & {{n = 31},32,\ldots\mspace{14mu},61}\end{matrix} \right.} & \left\lbrack {{Equation}\mspace{14mu} 1} \right\rbrack\end{matrix}$

In Equation 1, u denotes a root sequence index defined by Table 1.

TABLE 1 N_(ID) ⁽²⁾ Root index u 0 25 1 29 2 34

The sequence d(n) may be mapped to a Resource Element (RE), based onEquation 2.

$\begin{matrix}{{{a_{k,l} = {d(n)}},{n = 0},\ldots\mspace{14mu},61}{k = {n - 31 + \frac{N_{RB}^{DL}N_{sc}^{RB}}{2}}}} & \left\lbrack {{Equation}\mspace{14mu} 2} \right\rbrack\end{matrix}$

Here, a_(k,l) denotes an RE, k denotes a subcarrier number, and ldenotes an OFDM symbol number.

Mapping of a sequence used for the PSS to REs is determined based on aframe structure.

In the case of frame structure type 1 for Frequency Division Duplex(FDD), a PSS is mapped to the last OFDM symbol in slots 1 and 10 in asingle radio frame.

In the case of frame structure type 2 for Time Division Duplex (TDD), aPSS is mapped to the third OFDM symbol in subframes 1 and 6 in a singleradio frame.

Here, a single radio frame includes 10 subframes (subframes 0 to 9), andthis may correspond to 20 slots (slots 0 to 19) when a single subframeis formed of two slots. In addition, a single slot includes a pluralityof OFDM symbols.

An RE corresponding to Equation 3 from among REs (k, l) of OFDM symbolsmay not be used but may be reserved for transmission of a PSS.

$\begin{matrix}{{k = {n - 31 + \frac{N_{RB}^{DL}N_{sc}^{RB}}{2}}}{{n = {- 5}},{- 4},\ldots\mspace{14mu},{- 1},62,63,{\ldots\mspace{14mu} 66}}} & \left\lbrack {{Equation}\mspace{14mu} 3} \right\rbrack\end{matrix}$

A sequence d(0), . . . , d(61) used for an SSS may be generated byinterleaving two binary sequences having a length of 31.

The combination of two binary sequences having a length of 31, whichdefines the SSS, may have different values between a subframe 0 and asubframe 5, based on Equation 4.

$\begin{matrix}{\mspace{20mu}{{d\left( {2n} \right)} = \left\{ {{\begin{matrix}{{s_{0}^{(m_{0})}(n)}{c_{0}(n)}} & {{in}\mspace{14mu}{subframe}\mspace{14mu} 0} \\{{s_{1}^{(m_{1})}(n)}{c_{0}(n)}} & {{in}\mspace{14mu}{subfame}\mspace{14mu} 5}\end{matrix}{d\left( {{2n} + 1} \right)}} = \left\{ \begin{matrix}{{s_{1}^{(m_{1})}(n)}{c_{1}(n)}{z_{1}^{(m_{0})}(n)}} & {{in}\mspace{14mu}{subframe}\mspace{14mu} 0} \\{{s_{0}^{(m_{0})}(n)}{c_{1}(n)}{z_{1}^{(m_{1})}(n)}} & {{in}\mspace{14mu}{subfame}\mspace{14mu} 5}\end{matrix} \right.} \right.}} & \left\lbrack {{Equation}\mspace{14mu} 4} \right\rbrack\end{matrix}$

In Equation 4, n has a value that satisfies 0≤n≤30. m₀ and m₁ may beobtained from a physical layer cell identity (ID) group based onEquation 5.

$\begin{matrix}{{m_{0} = {m^{\prime}{mod}\; 31}}{m_{1} = {\left( {m_{0} + \left\lfloor {m^{\prime}/31} \right\rfloor + 1} \right){mod}\; 31}}{m^{\prime} = {N_{ID}^{(1)} + {{q\left( {q + 1} \right)}/2}}},{q = \left\lfloor \frac{N_{ID}^{(1)} + {{q^{\prime}\left( {q^{\prime} + 1} \right)}/2}}{30} \right\rfloor},{q^{\prime} = \left\lfloor {N_{ID}^{(1)}/30} \right\rfloor}} & \left\lbrack {{Equation}\mspace{14mu} 5} \right\rbrack\end{matrix}$

Result values of Equation 5 may be expressed, as listed in Table 2 andTable 3.

TABLE 2 N_(ID) ⁽¹⁾ m₀ m₁ 0 0 1 1 1 2 2 2 3 3 3 4 4 4 5 5 5 6 6 6 7 7 7 88 8 9 9 9 10 10 10 11 11 11 12 12 12 13 13 13 14 14 14 15 15 15 16 16 1617 17 17 18 18 18 19 19 19 20 20 20 21 21 21 22 22 22 23 23 23 24 24 2425 25 25 26 26 26 27 27 27 28 28 28 29 29 29 30 30 0 2 31 1 3 32 2 4 333 5 34 4 6 35 5 7 36 6 8 37 7 9 38 8 10 39 9 11 40 10 12 41 11 13 42 1214 43 13 15 44 14 16 45 15 17 46 16 18 47 17 19 48 18 20 49 19 21 50 2022 51 21 23 52 22 24 53 23 25 54 24 26 55 25 27 56 26 28 57 27 29 58 2830 59 0 3 60 1 4 61 2 5 62 3 6 63 4 7 64 5 8 65 6 9 66 7 10 67 8 11 68 912 69 10 13 70 11 14 71 12 15 72 13 16 73 14 17 74 15 18 75 16 19 76 1720 77 18 21 78 19 22 79 20 23 80 21 24 81 22 25 82 23 26 83 24 27 84 2528 85 26 29 86 27 30 87 0 4 88 1 5 89 2 6 90 3 7 91 4 8 92 5 9 93 6 1094 7 11 95 8 12 96 9 13 97 10 14 98 11 15 99 12 16 100 13 17 101 14 18

TABLE 3 N_(ID) ⁽¹⁾ m₀ m₁ 102 15 19 103 16 20 104 17 21 105 18 22 106 1923 107 20 24 108 21 25 109 22 26 110 23 27 111 24 28 112 25 29 113 26 30114 0 5 115 1 6 116 2 7 117 3 8 118 4 9 119 5 10 120 6 11 121 7 12 122 813 123 9 14 124 10 15 125 11 16 126 12 17 127 13 18 128 14 19 129 15 20130 16 21 131 17 22 132 18 23 133 19 24 134 20 25 135 21 26 136 22 27137 23 28 138 24 29 139 25 30 140 0 6 141 1 7 142 2 8 143 3 9 144 4 10145 5 11 146 6 12 147 7 13 148 8 14 149 9 15 150 10 16 151 11 17 152 1218 153 13 19 154 14 20 155 15 21 156 16 22 157 17 23 158 18 24 159 19 25160 20 26 161 21 27 162 22 28 163 23 29 164 24 30 165 0 7 166 1 8 167 29 — — — — — —

Two sequences s₀ ^((m) ⁰ ⁾(n) and s₁ ^((m) ¹ ⁾(n) may be defined as twodifferent cyclic shifts of an m-sequence {tilde over (s)}(n), based onEquation 6.s ₀ ^((m) ⁰ ⁾(n)={tilde over (s)}((n+m ₀)mod 31)s ₁ ^((m) ¹ ⁾(n)={tilde over (s)}((n+m ₁)mod 31)  [Equation 6]

Equation 6 satisfies {tilde over (s)}(i)=1−2x(i) and 0≤i≤30, and x(i)may be defined by Equation 7.x(ī+5)=(x(ī+2)+x(ī))mod 2,0≤ī≤25  [Equation 7]

In Equation 7, the initial value of x(i) may be set to x(0)=0, x(1)=0,x(2)=0, x(3)=0, x(4)=1.

c₀(n) and c₁(n), which are two scrambling sequences, may be determinedbased on a PSS, and may be defined by two different cyclic shifts of anm-sequence {tilde over (c)}(n) based on Equation 8.c ₀(n)={tilde over (c)}((n+N _(ID) ⁽²⁾)mod 31)c ₁(n)={tilde over (c)}((n+N _(ID) ⁽²⁾+3)mod 31)  [Equation 8]

In Equation 8, N_(ID) ⁽²⁾∈{0,1,2} is a physical layer ID in a physicallayer cell ID group N_(ID) ⁽¹⁾, Equation 8 satisfies {tilde over(c)}(i)=1−2x(i) and 0≤i≤30, and x(i) is defined by Equation 9.x(ī+5)=(x(ī+3)+x(ī))mod 2,0≤ī≤25  [Equation 9]

In Equation 9, the initial value of x(i) may be set to x(0)=0, x(1)=0,x(2)=0, x(3)=0, x(4)=1.

Scrambling sequences z₁ ^((m) ⁰ ⁾(n) and z₁ ^((m) ¹ ⁾(n) may be definedby a cyclic shift of an m-sequence {tilde over (z)}(n) based on Equation10.z ₁ ^((m) ⁰ ⁾(n)={tilde over (z)}((n+(m ₀ mod 8))mod 31)z ₁ ^((m) ¹ ⁾(n)={tilde over (z)}((n+(m ₁ mod 8))mod 31)  [Equation 10]

In Equation 10, m₀ and m₁ may be obtained through Table 2, and satisfy{tilde over (z)}(i)=1−2x(i) and 0≤i≤30, and x(i) may be defined byEquation 11.x(ī+5)=(x(ī+4)+x(ī+2)+x(ī+1)+x(ī))mod 2,0≤ī≤25  [Equation 11]

In Equation 11, the initial condition of x(i) may be set to x(0)=0,x(1)=0, x(2)=0, x(3)=0, x(4)=1.

Mapping of a sequence used for the SSS to REs is determined based on aframe structure.

The sequence d(n) may be mapped to REs based on Equation 12.

$\begin{matrix}{\mspace{20mu}{{{a_{k,l} = {d(n)}},{n = 0},\ldots\mspace{14mu},61}\mspace{20mu}{k = {n - 31 + \frac{N_{RB}^{DL}N_{sc}^{RB}}{2}}}{l = \left\{ \begin{matrix}{N_{symb}^{DL} - 2} & {{in}\mspace{14mu}{slots}\mspace{14mu} 0\mspace{14mu}{and}\mspace{14mu} 10\mspace{14mu}{for}\mspace{14mu}{frame}\mspace{14mu}{structuretype}\mspace{14mu} 1} \\{N_{symb}^{DL} - 1} & {{in}\mspace{14mu}{slots}\mspace{14mu} 1\mspace{14mu}{and}\mspace{14mu} 11\mspace{14mu}{for}\mspace{14mu}{frame}\mspace{14mu}{structuretype}\mspace{14mu} 2}\end{matrix} \right.}}} & \left\lbrack {{Equation}\mspace{14mu} 12} \right\rbrack\end{matrix}$

In Equation 12, a_(k,l) denotes an RE, k denotes a sub carrier number,and l denotes an OFDM symbol number.

An RE corresponding to Equation 13 from among REs (k, l) of OFDM symbolsmay not be used but may be reserved for transmission of an SSS.

$\begin{matrix}{\mspace{20mu}{{k = {n - 31 + \frac{N_{RB}^{DL}N_{sc}^{RB}}{2}}}{l = \left\{ {{{\begin{matrix}{N_{symb}^{DL} - 2} & {{in}\mspace{14mu}{slots}\mspace{14mu} 0\mspace{14mu}{and}\mspace{14mu} 10\mspace{14mu}{for}\mspace{14mu}{frame}\mspace{14mu}{structuretype}\mspace{14mu} 1} \\{N_{symb}^{DL} - 1} & {{in}\mspace{14mu}{slots}\mspace{14mu} 1\mspace{14mu}{and}\mspace{14mu} 11\mspace{14mu}{for}\mspace{14mu}{frame}\mspace{14mu}{structuretype}\mspace{14mu} 2}\end{matrix}\mspace{20mu} n} = {- 5}},{- 4},\ldots\mspace{14mu},{- 1},62,63,{\ldots\mspace{14mu} 66}} \right.}}} & \left\lbrack {{Equation}\mspace{14mu} 13} \right\rbrack\end{matrix}$

A D2DSS transmitted by a D2D synchronization source may include aPhysical Synchronization Source Identity (PSSID) and/or a type of a D2Dsynchronization source and a PD2DSS. The PD2DSS is based on a Zadoff Chusequence.

For a D2DSS, a PD2DSS may need to be defined. When a D2D synchronizationsource is an eNodeB, a D2DSS may be identical to a PSS/SSS. However,when a D2D synchronization source is different from an eNodeB, a newtype of PD2DSS needs to be defined.

It should be avoided that UEs erroneously interpret a D2DSS that istransmitted by a D2D synchronization source that is different from aneNodeB, as typical DL synchronization signals such as a PSS or an SSS.If a UE misinterprets received D2DSS as a DL synchronization signaltypically transmitted from an eNodeB, the D2D synchronization source,which transmitted the D2DSS, may be erroneously recognized as an eNodeBby the UE or synchronization information may be incorrectly recognizedby the UE. Therefore, a sequence used by the D2DSS should be differentfrom a sequence that is used in the cellular communication (or asequence for a PSS or an SSS). To this end, a sequence of which a rootindex is different from a sequence of a cellular communication may bedefined and used.

When a D2D synchronization source is an eNodeB, a PD2DSS transmitted bythe synchronization source is a PSS (Primary Synchronization Signal).When a D2D synchronization source is different from the eNodeB, a PD2DSStransmitted by the synchronization source may be defined based on thefeatures described herein. The PD2DSS may incorporate one or morefeatures of the PSS. For example, when the D2D synchronization source isa UE, a broadcasting UE, a cluster head, a synchronization head, or thelike, a D2DSS which is modified from a PSS (hereinafter referred to as aPD2DSS) may be configured.

When a D2D synchronization source is different from an eNodeB, one ormore exemplary embodiments may provide a method of generating a sequenceof a PD2DSS transmitted by the D2D synchronization source, using one ofadditional three root indices in addition to general three root indicesdefined for a PSS. For example, the root indices of Table 4 may be used.

TABLE 4 Example No. Root Index Example 1 38, 26, 37 Example 2 38, 23, 40Example 3 38, 19, 44 Example 4 38, 16, 47 Example 5 38, 5, 58 Example 638, 2, 61

According to one or more exemplary embodiments, a transmission D2Dsynchronization source may be defined as a node that transmits a D2Ddirect synchronization signal to a UE, and may also be referred to as atransmission (Tx) synchronization source. For example, in FIG. 1, atransmission synchronization source for the first UE 110 may be a firsteNodeB 100, and a transmission synchronization source for the second UE120 may be the first UE 110 or a second eNodeB 160.

According to one or more exemplary embodiments, an original D2Dsynchronization source may be defined as a node that originate a D2Dsynchronization signal, and may also be referred to as an originalsynchronization source. For example, in FIG. 1, an originalsynchronization source for the second UE 120 may be the first eNodeB 100or the second eNodeB 160.

According to one or more exemplary embodiments, an IndependentSynchronization Source (ISS) may be defined as a D2D synchronizationsource which is not an eNodeB but generates a D2D synchronization signalby itself. For example, In FIG. 1, the fifth UE 150 may be an ISS.

According to one or more exemplary embodiments, a hop count indicatesthe number of stages in which a synchronization signal is transmittedfrom a synchronization source to a UE, and may be increased by 1 foreach stage. Referring to FIG. 1, when the eNodeB 100 transmits asynchronization signal to the second UE 120 through the first UE 110, ahop count to the first UE 110 is 1 and a hop count to the second UE 120is 2.

A stratum level indicates the number of stages in which asynchronization signal is transmitted from a synchronization sourcerecognized by a system to a UE. The stratum level may be identical to ahop count, and may be smaller than the hop count when a hop count thatis not recognized by a system exists.

A PD2DSCH indicates a physical D2D synchronization channel, andaccording to one or more exemplary embodiments, the PD2DSCH may be usedto indicate information, such as, a type of a synchronization source, aPhysical Synchronization Source Identity (PSSID), or a stratum level.

A cell ID may include a plurality of unique physical layer cell IDs, forexample, 504 physical layer cell IDs. The physical layer cell IDs N_(ID)^(cell) may be grouped into 168 unique physical layer cell ID groups,and each group includes three unique IDs. Therefore, a physical layercell ID may have a unique value defined by N_(ID) ^(cell)=3N_(ID)⁽¹⁾+N_(ID) ⁽²⁾ which is an integer in a range from 0 to 167 expressing aphysical layer cell ID group and N_(ID) ⁽¹⁾ which is an integer in arange from 0 to 2 expressing a physical layer ID in a physical layercell ID group, as shown in N_(ID) ⁽²⁾.

Embodiments provided below describe a method of transmittingsynchronization information such as the type of synchronization source,a Physical Synchronization Source Identity (PSSID), a stratum level, orthe like, through use of a PD2DSS, an SD2DSS, the location of a D2DSS ina subframe, and a PD2DSCH.

FIG. 2 is a conceptual diagram of a system to which a method oftransmitting a synchronization signal is applied according to one ormore exemplary embodiments. The upper portion of FIG. 2 illustratessynchronization signal transmissions executed from an eNodeB 200 to afirst UE, from the first UE 210 to a second UE 220, and from the secondUE 220 to a third UE 230, respectively. The eNodeB 200 may be anoriginal Synchronization Source (original SS) for the first UE 210, thesecond UE 220, and the third UE 230. The eNodeB 200 may be atransmission synchronization source (Tx SS) for the first UE 210, thefirst UE 210 may be a Tx SS for the second UE 220, and the second UE 220may be a Tx SS for the third UE 230.

Referring to the lower portion of FIG. 2, a fourth UE 240 may notreceive a synchronization signal from an eNodeB or another UE, butgenerate a synchronization signal by itself and transmit the same toanother UE, and thus, the fourth UE 240 corresponds to an ISS. Thefourth UE 240 may transmit a synchronization signal to a fifth UE 250,and the fifth UE 250 transmits a synchronization signal to a sixth UE260, and the sixth UE 260 transmits a synchronization signal to aseventh UE 270, respectively. The fourth UE 240 may be an originalSynchronization Source (original SS) for the fifth UE 250, the sixth UE260, and the seventh UE 270. The fourth UE 240 may be a transmissionsynchronization source (Tx SS) for the fifth UE 250, the fifth UE 250may be a Tx SS for the sixth UE 260, and the sixth UE 260 may be a Tx SSfor the seventh UE 270.

Referring to FIG. 2, a stratum level when a synchronization signaldeparting from the eNodeB 200 is transmitted to the first UE 210, isreferred to as a first stratum, and a stratum level when thesynchronization signal is transmitted to the second UE 220 via the firstUE 210, is referred to as a second stratum. In the same manner, astratum level when the synchronization signal is transmitted to thethird UE 230 via the first UE 210 and the second UE 220, is referred toas a third stratum.

One or more exemplary embodiments presented herein may be modified orvaried by incorporating one or more features from other exemplaryembodiments or configurations not explicitly described in thisdisclosure.

Embodiments 1-1 to 1-5 describe a method of indicating D2Dsynchronization information when the maximum stratum level is a thirdstratum in the case where an original synchronization source is aneNodeB, and when the maximum stratum level is a third stratum in thecase where the original synchronization source is an ISS.

[Embodiment 1-1]

TABLE 5 Type of SS Stratum level case Tx SS original SS PSSID (hopcount) case 1: eNodeB→UE₁ eNodeB PCID 1^(st) eNodeB eNodeB of eNodeB(Index 0 (or 1)) case 2: eNodeB→UE₁→UE₂ SS relaying eNodeB PCID 2^(nd)UE (=UE₁) eNodeB of eNodeB (Index 1 (or 2)) case 3: SS relaying eNodeBPCID 3^(rd) eNodeB→UE₁→UE₂→UE₃ UE (=UE₂) eNodeB of eNodeB (Index 2 (or3)) case 4: ISS (=UE_(A))→UE_(B) ISS based on 1^(st) UE (=UE_(A)) ISS(=UE_(A)) ISS (=UE_(A)) (Index 0 (or 1)) ID case5: ISS(=UE_(A))→UE_(B)→UE_(C) SS relaying ISS based on 2^(nd) UE (=UE_(B)) ISS(=UE_(A)) ISS (=UE_(A)) (Index 1 (or 2)) ID case 6: SS relaying ISSbased on 3^(rd) ISS (=UE_(A))→UE_(B)→UE_(C)→UE_(D) UE (=UE_(C)) ISS(=UE_(A)) ISS (=UE_(A)) (Index 2 (or 3)) ID

In the present embodiment, when a type of a Synchronization Source (SS)is an eNodeB or an SS derived from an eNodeB (an SS relaying an eNodeB),a PCID of an eNodeB may be used as a Physical Synchronization SourceIdentity (PSSID), and 504 unique PSSIDs may exist.

When a type of a Synchronization Source (SS) is an ISS or an SS derivedfrom an ISS (an SS relaying an ISS), a PSSID based on a UE ID of the ISSmay be used and 504 unique PSSIDs may exist.

In the present embodiment, a type of a transmission synchronizationsource may be indicated by a root index value of a PD2DSS. For example,the cases of Table 5 may be classified into two cases, that is, a casecorresponding to Case 1 in which a transmission synchronization sourceis an eNodeB and the other case corresponding to Cases 2 to 6 in which atransmission synchronization source is a UE, and each case may beindicated by a root index value of a PD2DSS. A PD2DSS when thetransmission synchronization source is an eNodeB, may use 25, 29, and34, which are identical to the root indices of a PSS. A PD2DSS when thetransmission synchronization source is a UE, may use newly defined rootindices which are different from the root indices of a PSS. For example,the root indices of Table 4 may be used.

When the transmission synchronization source is a UE, a type of anoriginal synchronization source may be indicated by a Physical D2DSynchronization Channel (PD2DSCH). For example, the cases of Table 5 maybe indicated based on the classification into two cases, that is, a casecorresponding to Cases 2 and 3 in which a type of an originalsynchronization source is an eNodeB and the other case corresponding toCases 4 to 6 in which a type of an original synchronization source is anIndependent Synchronization Source (ISS). Therefore, an indication valueof the PD2DSCH may have a one-bit value. When the transmissionsynchronization source is an eNodeB, it may be recognized that theoriginal synchronization source is the eNodeB, through a root indexvalue of the PD2DSS, and thus, this may not need to be indicatedseparately.

In addition, when the transmission synchronization source is a UE, astratum level may be indicated by a location where a D2DSS istransmitted in a frequency-resource domain or a PD2DSCH. For example,the cases of Table 5 may be indicated based on the classification intothree cases, that is, a case corresponding to Case 4 in which a stratumlevel is 1, another case corresponding to Cases 2 and 5 in which astratum level is 2, and the other case corresponding to Cases 3 and 6 inwhich a stratum level is 3.In this instance, therefore, an indicationvalue of the PD2DSCH may have a two-bit value. When the transmissionsynchronization source is an eNodeB, the stratum level may be recognizedthrough a root index value of the PD2DSS, and thus, this may not need tobe indicated separately.

When a type of the synchronization source is an eNodeB, a physical layercell ID (N_(ID) ^(cell)) corresponding to a PCID of the eNodeB may beused as a Physical Synchronization Source Identity (PSSID). The physicallayer cell ID may be expressed as N_(ID) ^(cell)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾,and N_(ID) ⁽²⁾ may be mapped in one-to-one correspondence to rootindices of the PD2DSS that may have three values, and may have aninteger in a range from 0 to 2. In this instance, the root index of thePD2DSS may have one of 25, 29, and 34, which are identical to the rootindices of the PSS. N_(ID) ⁽¹⁾ may be mapped in one-to-onecorrespondence to root indices of an SD2DSS that may have 168 values,and may have an integer in a range from 0 to 167. In this instance, avalue that is identical to the SSS may be used as the value of theSD2DSS.

Even when the type of the synchronization source is a synchronizationsource derived from an eNodeB, a Physical Synchronization SourceIdentity (PSSID) may have a value identical to a PCID of an eNodeB, and504 unique PSSIDs may exist. The PSSID may be expressed as N_(ID)^(D2D)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾, and N_(ID) ⁽²⁾ may be mapped inone-to-one correspondence to root indices of a PD2DSS that may havethree values, and may have an integer in a range from 0 to 2. In thisinstance, newly defined root indices which are different from the rootindices of the PSS may be used as a root index of the PD2DSS, and forexample, the root indices of Table 4 may be used. For N_(ID) ⁽¹⁾, avalue of an SD2DSS that is mapped in one-to-one correspondence to an SSShaving 168 sequences may be used. Therefore, the SD2DSS may have aninteger in a range from 0 to 167, and a PSSID may be mapped to504(=3*168) IDs.

When the type of the synchronization source is an ISS or asynchronization source derived from an ISS, a Proximity based Services(ProSe) UE ID of a UE corresponding to the ISS may be used as a PhysicalSynchronization Source Identity (PSSID), and the PSSID may be mapped to504 IDs based on a predetermined mapping rule. The PSSID may beexpressed as N_(ID) ^(D2D)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾, and N_(ID) ⁽²⁾ may bemapped in one-to-one correspondence to root indices of the PD2DSS thatmay have three values, and may have an integer in a range from 0 to 2.In this instance, newly defined root indices which are different fromthe root indices of the PSS may be used as a root index of the PD2DSS,and for example, the root indices of Table 4 may be used. N_(ID) ⁽¹⁾associated with the SD2DSS may be mapped in one-to-one correspondence toan SSS having 168 sequences and may have an integer in a range from 0 to167. Therefore, the PSSID may be mapped to 504(=3*168) IDs.

[Embodiment 1-2]

TABLE 6 Type of SS Stratum level case Tx SS Original SS PSSID (hopcount) case 1: eNodeB→UE₁ eNodeB PCID 1^(st) eNodeB eNodeB of eNodeB(Index 0 (or 1)) case 2: eNodeB→UE₁→UE₂ SS relaying eNodeB based on2^(nd) UE (=UE₁) eNodeB PCID (Index 1 (or 2)) of eNodeB case 3:eNodeB→UE₁→UE₂→UE₃ SS relaying eNodeB based on 3^(rd) UE (=UE₂) eNodeBPCID (Index 2 (or 3)) of eNodeB case 4: ISS (=UE_(A))→UE_(B) ISS basedon 1^(st) UE (=UE_(A)) ISS (=UE_(A)) ISS (=UE_(A)) (Index 0 (or 1)) IDcase 5: ISS (=UE_(A))→UE_(B)→UE_(C) SS relaying ISS based on 2^(nd) UE(=UE_(B)) ISS (=UE_(A)) ISS (=UE_(A)) (Index 1 (or 2)) ID case 6: SSrelaying ISS based on 3^(rd) ISS (=UE_(A))→UE_(B)→UE_(C)→UE_(D) UE(=UE_(C)) ISS (=UE_(A)) ISS (=UE_(A)) (Index 2 (or 3)) ID

In the present embodiment, when the type of the Synchronization Source(SS) is an eNodeB, a PCID of the eNodeB may be used as a PSSID, and 504unique PSSIDs may be used. When the type of the synchronization sourceis an SS derived from an eNodeB (an SS relaying an eNodeB), a valuemodified based on the PCID of the eNodeB may be used as a PSSID, and 168or K unique PSSIDs may exist, wherein K is a value that is less than168.

When the type of the Synchronization Source (SS) is an ISS or an SSderived from an ISS (an SS relaying an ISS), a PSSID may be determinedbased on a UE ID of the ISS, and 168 or K unique PSSIDs may exist,wherein K is a value that is less than 168.

In the present embodiment, a transmission synchronization source isindicated by a root index value of a PD2DSS and a stratum level when thetransmission synchronization source is an eNodeB is 1 and thus, thestratum level may not need to be indicated separately.

When the transmission synchronization source is a UE, a stratum levelmay be indicated by a root index of a PD2DSS. For example, the cases ofTable 6 may be indicated based on the classification into three cases,that is, a case corresponding to Case 4 in which a stratum level is 1,another case corresponding to Cases 2 and 5 in which a stratum level is2, and the other case corresponding to Cases 3 and 6 in which a stratumlevel is 3. Therefore, when three newly defined root indices of a PD2DSSare X, Y, and Z, respectively, for example, a root index X may be set toindicate a stratum level 1, a root index Y may be set to indicate astratum level 2, and a root index Z may be set to indicate a stratumlevel 3. The root indices of Table 4 may be used as the newly definedroot indices of the PD2DSS.

When the type of the synchronization source is an eNodeB (Case 1), aphysical layer cell ID (N_(ID) ^(cell)) corresponding to a PCID of theeNodeB may be used as a Physical Synchronization Source Identity(PSSID). The physical layer cell ID may be expressed as N_(ID)^(cell)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾, and N_(ID) ⁽²⁾ may be mapped inone-to-one correspondence to root indices of the PD2DSS that may havethree values, and may have an integer in a range from 0 to 2. In thisinstance, the root index of the PD2DSS may have one of 25, 29, and 34,which are identical to the root indices of the PSS. N_(ID) ⁽¹⁾ may bemapped in one-to-one correspondence to root indices of an SD2DSS thatmay have 168 values, and may have an integer in a range from 0 to 167.In this instance, a value that is identical to the SSS may be used asthe value of the SD2DSS.

When the type of the synchronization source is a synchronization sourcederived from an eNodeB (an SS relaying an eNodeB) (Cases 2 and 3), aPhysical Synchronization Source Identity (PSSID) may be mapped to 168 orK IDs based on a PCID of the eNodeB using a predetermined rule, whereinK is a value that is less than 168. Therefore, the PSSID may have avalue in a range from 0 to 167 or in a range from 0 to K-1. The PSSIDmay be expressed as N_(ID) ^(D2D)=N_(ID) ⁽¹⁾, and N_(ID) ⁽¹⁾ associatedwith the SD2DSS may be mapped in one-to-one correspondence to an SSSthat may have 168 values, and may have an integer in a range from 0 to167, or may be mapped in one-to-one correspondence to K values, based onsequences that are modified or partially selected from an SSS having 168sequences and may have an integer in a range from 0 to K-1, wherein K isa value less than 168. In this instance, an accurate PCID of the eNodeBmay be transmitted through a PD2DSCH.

When the type of the synchronization source is an ISS or asynchronization source derived from an ISS (Cases 4, 5, and 6), aProximity based Services (ProSe) UE ID of a UE corresponding to the ISSmay be used as a Physical Synchronization Source Identity (PSSID), andthe PSSID may be mapped to 168 or K IDs based on a predetermined mappingrule, wherein K is a value that is less than 168. Therefore, the PSSIDmay have a value in a range from 0 to 167 or in a range from 0 to K-1.The PSSID may be expressed as N_(ID) ^(D2D)=N_(ID) ⁽¹⁾, and N_(ID) ⁽¹⁾associated with the SD2DSS may be mapped in one-to-one correspondence toan SSS that may have 168 values, and may have an integer in a range from0 to 167, or may be mapped in one-to-one correspondence to K values,based on sequences that are modified or partially selected from an SSShaving 168 sequences and may have an integer in a range from 0 to K-1,wherein K is a value less than 168. In this instance, an accurate UE IDof the ISS may be transmitted through a PD2DSCH.

[Embodiment 1-3]

TABLE 7 Type of SS Stratum level case Tx SS Original SS PSSID (hopcount) Case 1: eNodeB→UE₁ eNodeB PCID 1^(st) eNodeB eNodeB of eNodeB(Index 0 (or 1)) Case 2: eNodeB→UE₁→UE₂ SS relaying eNodeB PCID 2^(nd)UE (=UE₁) eNodeB of eNodeB (Index 1 (or 2)) Case 3: SS relaying eNodeBPCID 3^(rd) eNodeB→UE₁→UE₂→UE₃ UE (=UE₂) eNodeB of eNodeB (Index 2 (or3)) Case 4: ISS (=UE_(A))→UE_(B) ISS Based on 1^(st) UE (=UE_(A)) ISS(=UE_(A)) ISS (=UE_(A)) (Index 0 (or 1)) ID Case 5: SS relaying ISSBased on 2^(nd) ISS (=UE_(A))→UE_(B)→UE_(C) UE (=UE_(B)) ISS (=UE_(A))ISS (=UE_(A)) (Index 1 (or 2)) ID Case 6: SS relaying ISS Based on3^(rd) ISS (=UE_(A))→UE_(B)→UE_(C)→UE_(D) UE (=UE_(C)) ISS (=UE_(A)) ISS(=UE_(A)) (Index 2 (or 3)) ID

In the present embodiment, when a type of a Synchronization Source (SS)is an eNodeB or an SS derived from an eNodeB (an SS relaying an eNodeB),a PCID of an eNodeB may be used as a Physical Synchronization SourceIdentity (PSSID), and 504 unique PSSIDs may exist.

When the type of the Synchronization Source (SS) is an ISS or an SSderived from an ISS (an SS relaying an ISS), a PSSID based on a UE ID ofthe ISS may be used, and 168 or K unique PSSIDs may exist, wherein K isa value that is less than 168.

In the present embodiment, a type of a transmission synchronizationsource may be indicated by a root index value of a PD2DSS. For example,cases of Table 7 may be classified into two cases, that is, a casecorresponding to Case 1 in which a transmission synchronization sourceis an eNodeB and the other case corresponding to Cases 2 to 6 in which atransmission synchronization source is a UE, and each case may beindicated by a root index value of a PD2DSS. A PD2DSS when thetransmission synchronization source is an eNodeB, may use 25, 29, and34, which are identical to the root indices of a PSS. A PD2DSS when thetransmission synchronization source is a UE may use newly defined rootindices which are different from the root indices of a PSS. For example,the root indices of Table 4 may be used.

When the transmission synchronization source is a UE, a type of anoriginal synchronization source may be indicated by a Physical D2DSynchronization Channel (PD2DSCH). For example, the cases of Table 7 maybe indicated based on the classification into two cases, that is, a casecorresponding to Cases 2 and 3 in which a type of an originalsynchronization source is an eNodeB and a case corresponding to Cases 4to 6 in which a type of an original synchronization source is anIndependent Synchronization Source (ISS). Therefore, an indication valueof the PD2DSCH may have a 1-bit value. When the transmissionsynchronization source is an eNodeB, it may be recognized that theoriginal synchronization source is the eNodeB, through a root indexvalue of the PD2DSS, and thus, this may not need to be indicatedseparately.

In addition, when the original synchronization source is an eNodeB andthe transmission synchronization source is a UE, a stratum level may beindicated by a location where a D2DSS is transmitted in afrequency-resource domain or a PD2DSCH. For example, cases of Table 7may be indicated based on the classification into two cases, that is, acase corresponding to Case 2 in which a stratum level is 2 and a casecorresponding to Case 3 in which a stratum level is 3. Therefore, anindication value of the PD2DSCH may have a 1-bit value. Here, 1-bitinformation of the PD2DSCH may be designed to be different based on thecoverage scenario, and the 1-bit information of the PD2DSCH may bedesigned to not be included in an out-of-coverage. Therefore, in Cases 4to 6 in which the original synchronization source is an ISS, a stratumlevel may be indicated by a root index value of a PD2DSS, as opposed toby the PD2DSH. When the transmission synchronization source is aneNodeB, the stratum level may be recognized through a root index valueof the PD2DSS, and thus, this may not need to be indicated separately.

When the original synchronization source is an ISS, a stratum level maybe indicated by a root index of a PD2DSS. Cases 4 to 6 of Table 7 may beindicated based on the classification into a total of three cases, basedon a stratum level. Therefore, when three newly defined root indices ofa PD2DSS are X, Y, and Z, respectively, for example, a root index X maybe set to indicate a stratum level 1, a root index Y may be set toindicate a stratum level 2, and a root index Z may be set to indicate astratum level 3. The root indices of Table 4 may be used as the newlydefined root indices of the PD2DSS.

When a type of the synchronization source is an eNodeB, a physical layercell ID (N_(ID) ^(cell)) corresponding to a PCID of the eNodeB may beused as a Physical Synchronization Source Identity (PSSID). The physicallayer cell ID may be expressed as N_(ID) ^(cell)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾,and N_(ID) ⁽²⁾ may be mapped in one-to-one correspondence to rootindices of the PD2DSS that may have three values, and may have aninteger in a range from 0 to 2. In this instance, the root index of thePD2DSS may have one of 25, 29, and 34, which are identical to the rootindices of the PSS. N_(ID) ⁽¹⁾ may be mapped in one-to-onecorrespondence to root indices of an SD2DSS that may have 168 values,and may have an integer in a range from 0 to 167. In this instance, avalue that is identical to the SSS may be used as the value of theSD2DSS.

Even when the type of the synchronization source is a synchronizationsource derived from an eNodeB, a Physical Synchronization SourceIdentity (PSSID) may have a value identical to the PCID of the eNodeB,and 504 unique PSSaIDs may exist. The PSSID may be expressed as N_(ID)^(D2D)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾, and N_(ID) ⁽²⁾ may be mapped inone-to-one correspondence to root indices of the PD2DSS that may havethree values, and may have an integer in a range from 0 to 2. In thisinstance, newly defined root indices which are different from the rootindices of the PSS may be used as a root index of the PD2DSS, and forexample, the root indices of Table 4 may be used. For N_(ID) ⁽¹⁾, avalue of an SD2DSS that is mapped in one-to-one correspondence to an SSShaving 168 sequences may be used. Therefore, the SD2DSS may have aninteger in a range from 0 to 167, and a PSSID may be mapped to504(=3*168) IDs.

When the type of the synchronization source is an ISS or asynchronization source derived from an ISS (Cases 4, 5, and 6), aProximity based Services (ProSe) UE ID of a UE corresponding to the ISSmay be used as a Physical Synchronization Source Identity (PSSID), andthe PSSID may be mapped to 168 or K IDs based on a predetermined mappingrule, wherein K is a value that is less than 168. Therefore, the PSSIDmay have a value in a range from 0 to 167 or in a range from 0 to K-1.The PSSID may be expressed as N_(ID) ^(D2D)=N_(ID) ⁽¹⁾, and N_(ID) ⁽¹⁾associated with the SD2DSS may be mapped in one-to-one correspondence toan SSS that may have 168 values, and may have an integer in a range from0 to 167, or may be mapped in one-to-one correspondence to K values,based on sequences that are modified or partially selected from an SSShaving 168 sequences and may have an integer in a range from 0 to K-1,wherein K is a value less than 168. In this instance, an accurate UE IDof the ISS may be transmitted through a PD2DSCH.

[Embodiment 1-4]

TABLE 8 Type of SS Stratum level Case Tx SS Original SS PSSID (hopcount) Case 1: eNodeB→UE₁ eNodeB PCID 1^(st) eNodeB eNodeB of eNodeB(Index 0 (or 1)) Case 2: eNodeB→UE₁→UE₂ SS relaying eNodeB Based on2^(nd) UE (=UE₁) eNodeB UE (=UE₁) ID (Index 1 (or 2)) Case 3: SSrelaying eNodeB Based on 3^(rd) eNodeB→UE₁→UE₂→UE₃ UE (=UE₂) eNodeB UE(=UE₂) ID (Index 2 (or 3)) Case 4: ISS (=UE_(A))→UE_(B) ISS Based on1^(st) UE (=UE_(A)) ISS (=UE_(A)) UE (=UE_(A)) ID (Index 0 (or 1)) Case5: ISS (=UE_(A))→UE_(B)→UE_(C) SS relaying ISS Based on 2^(nd) UE(=UE_(B)) ISS (=UE_(A)) UE (=UE_(B)) ID (Index 1 (or 2)) Case 6: SSrelaying ISS Based on 3^(rd) ISS (=UE_(A))→UE_(B)→UE_(C)→UE_(D) UE(=UE_(C)) ISS (=UE_(A)) UE (=UE_(C)) ID (Index 2 (or 3))

In the present embodiment, when the type of the Synchronization Source(SS) is an eNodeB, a PCID of an eNodeB may be used as a PhysicalSynchronization Source Identity (PSSID), and 504 unique PSSIDs mayexist.

When a type of a Synchronization Source (SS) is an SS derived from aneNodeB (an SS relaying an eNodeB), an ISS, or an SS derived from an ISS(an SS relaying an ISS), a PSSID based on a UE ID of a transmissionsynchronization source may be used, and 504 unique PSSIDs may exist.

In the present embodiment, a type of a transmission synchronizationsource may be indicated by a root index value of a PD2DSS. For example,cases of Table 8 may be classified into two cases, that is, a casecorresponding to Case 1 in which a transmission synchronization sourceis an eNodeB and the other case corresponding to Cases 2 to 6 in which atransmission synchronization source is a UE, and each case may beindicated by a root index value of a PD2DSS. A PD2DSS when thetransmission synchronization source is an eNodeB, may use 25, 29, and34, which are identical to the root indices of a PSS A PD2DSS when thetransmission synchronization source is a UE, may use newly defined rootindices which are different from the root indices of a PSS. For example,the root indices of Table 4 may be used.

When the transmission synchronization source is a UE, a type of anoriginal synchronization source may be indicated by a Physical D2DSynchronization Channel (PD2DSCH). For example, the cases of Table 8 maybe indicated based on the classification into two cases, that is, a casecorresponding to Cases 2 and 3 in which a type of an originalsynchronization source is an eNodeB and a case corresponding to Cases 4to 6 in which a type of an original synchronization source is anIndependent Synchronization Source (ISS). Therefore, an indication valueof the PD2DSCH may have a one-bit value. When the transmissionsynchronization source is an eNodeB, it may be recognized that theoriginal synchronization source is the eNodeB, through a root indexvalue of the PD2DSS, and thus, this may not need to be indicatedseparately.

In addition, when the transmission synchronization source is a UE, astratum level may be indicated by a location where a D2DSS istransmitted in a frequency-resource domain or a PD2DSCH. For example,the cases of Table 8 may be indicated based on the classification intothree cases, that is, a case corresponding to Case 4 in which a stratumlevel is 1, another case corresponding to Cases 2 and 5 in which astratum level is 2, and the other case corresponding to Cases 3 and 6 inwhich a stratum level is 3. Therefore, an indication value of thePD2DSCH may have a 2-bit value. When the transmission synchronizationsource is an eNodeB, the stratum level may be recognized through a rootindex value of the PD2DSS and thus, this may not need to be indicatedseparately.

When a type of the synchronization source is an eNodeB, a physical layercell ID (N_(ID) ^(cell)) corresponding to a PCID of the eNodeB may beused as a Physical Synchronization Source Identity (PSSID). The physicallayer cell ID may be expressed as N_(ID) ^(cell)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾,and N_(ID) ⁽²⁾ may be mapped in one-to-one correspondence to rootindices of the PD2DSS that may have three values, and may have aninteger in a range from 0 to 2. In this instance, the root index of thePD2DSS may have one of 25, 29, and 34, which are identical to the rootindices of the PSS. N_(ID) ⁽¹⁾ may be mapped in one-to-onecorrespondence to root indices of an SD2DSS that may have 168 values,and may have an integer in a range from 0 to 167. In this instance, avalue that is identical to the SSS may be used as the value of theSD2DSS.

When the type of the synchronization source is a synchronization sourcederived from an eNodeB (an SS relaying an eNodeB), an ISS, or asynchronization source derived from an ISS (an SS relaying an ISS), aProximity based Services (ProSe) UE ID of a transmission (Tx) UE may beused as a Physical Synchronization Source Identity (PSSID), and thePSSID may be mapped to 504 IDs based on a predetermined mapping rule.The PSSID may be expressed as N_(ID) ^(D2D)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾, andN_(ID) ⁽²⁾ may be mapped in one-to-one correspondence to root indices ofthe PD2DSS that may have three values, and may have an integer in arange from 0 to 2. In this instance, newly defined root indices whichare different from the root indices of the PSS may be used as a rootindex of the PD2DSS, and for example, the root indices of Table 4 may beused. N_(ID) ⁽¹⁾ associated with the SD2DSS may be mapped in one-to-onecorrespondence to an SSS having 168 sequences and may have an integer ina range from 0 to 167. Therefore, the PSSID may be mapped to 504(=3*168)IDs.

[Embodiment 1-5]

TABLE 9 Type of SS Stratum level Case Tx SS Original SS PSSID (hopcount) Case 1: eNodeB→UE₁ eNodeB PCID of 1^(st) eNodeB eNodeB eNodeB(Index 0 (or 1)) Case 2: eNodeB→UE₁→UE₂ SS relaying eNodeB Based on2^(nd) UE (=UE₁) eNodeB UE (=UE₁) ID (Index 1 (or 2)) Case 3: SSrelaying eNodeB Based on 3^(rd) eNodeB→UE₁→UE₂→UE₃ UE (=UE₂) eNodeB UE(=UE₂) ID (Index 2 (or 3)) Case 4: ISS (=UE_(A))→UE_(B) ISS Based on1^(st) UE (=UE_(A)) ISS (=UE_(A)) UE (=UE_(A)) ID (Index 0 (or 1)) Case5: ISS (=UE_(A))→UE_(B)→UE_(C) SS relaying ISS Based on 2^(nd) UE(=UE_(B)) ISS (=UE_(A)) UE (=UE_(B)) ID (Index 1 (or 2)) Case 6: SSrelaying ISS Based on 3^(rd) ISS (=UE_(A))→UE_(B)→UE_(C)→UE_(D) UE(=UE_(C)) ISS (=UE_(A)) UE (=UE_(C)) ID (Index 2 (or 3))

In the present embodiment, when the type of the Synchronization Source(SS) is an eNodeB, a PCID of the eNodeB may be used as a PhysicalSynchronization Source Identity (PSSID), and 504 unique PSSIDs mayexist.

When a type of a Synchronization Source (SS) is an SS derived from aneNodeB (an SS relaying an eNodeB), an ISS, or an SS derived from an ISS(an SS relaying an ISS), a PSSID based on a UE ID of a transmissionsynchronization source may be used, and 168 or K unique PSSIDs mayexist, wherein K is a value less than 168.

In the present embodiment, a type of a transmission synchronizationsource may be indicated by a root index value of a PD2DSS. For example,cases of Table 9 may be classified into two cases, that is, a casecorresponding to Case 1 in which a transmission synchronization sourceis an eNodeB and the other case corresponding to Cases 2 to 6 in which atransmission synchronization source is a UE, and each case may beindicated by a root index value of a PD2DSS. A PD2DSS when thetransmission synchronization source is an eNodeB, may use 25, 29, and34, which are identical to the root indices of a PSS A PD2DSS when thetransmission synchronization source is a UE may use newly defined rootindices which are different from the root indices of a PSS. For example,the root indices of Table 4 may be used.

When the transmission synchronization source is a UE, a type of anoriginal synchronization source may be indicated by a Physical D2DSynchronization Channel (PD2DSCH). For example, the cases of Table 9 maybe indicated based on the classification into two cases, that is, a casecorresponding to Cases 2 and 3 in which a type of an originalsynchronization source is an eNodeB and a case corresponding to Cases 4to 6 in which a type of an original synchronization source is anIndependent Synchronization Source (ISS). Therefore, an indication valueof the PD2DSCH may have a one-bit value. When the transmissionsynchronization source is an eNodeB, it may be recognized that theoriginal synchronization source is the eNodeB, through a root indexvalue of the PD2DSS, and thus, this may not need to be indicatedseparately.

When the transmission synchronization source is a UE, a stratum levelmay be indicated by a root index of a PD2DSS. For example, the cases ofTable 9 may be indicated based on the classification into three cases,that is, a case corresponding to Case 4 in which a stratum level is 1,another case corresponding to Cases 2 and 5 in which a stratum level is2, and the other case corresponding to Cases 3 and 6 in which a stratumlevel is 3.

Therefore, when three newly defined root indices of a PD2DSS are X, Y,and Z, respectively, for example, a root index X may be set to indicatea stratum level 1, a root index Y may be set to indicate a stratum level2, and a root index Z may be set to indicate a stratum level 3. The rootindices of Table 4 may be used as the newly defined root indices of thePD2DSS.

When a type of the synchronization source is an eNodeB, a physical layercell ID (N_(ID) ^(cell)) corresponding to a PCID of the eNodeB may beused as a Physical Synchronization Source Identity (PSSID). The physicallayer cell ID may be expressed as N_(ID) ^(cell)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾,and N_(ID) ⁽²⁾ may be mapped in one-to-one correspondence to rootindices of the PD2DSS that may have three values, and may have aninteger in a range from 0 to 2. In this instance, the root index of thePD2DSS may have one of 25, 29, and 34, which are identical to the rootindices of the PSS. N_(ID) ⁽¹⁾ may be mapped in one-to-onecorrespondence to root indices of an SD2DSS that may have 168 values,and may have an integer in a range from 0 to 167. In this instance, avalue that is identical to the SSS may be used as the value of theSD2DSS.

When the type of the synchronization source is a synchronization sourcederived from an eNodeB (an SS relaying an eNodeB), an ISS, or asynchronization source derived from an ISS (an SS relaying an ISS), aProximity based Services (ProSe) UE ID of a transmission (Tx) UE may beused as a Physical Synchronization Source Identity (PSSID), and thePSSID may be mapped to 168 or K IDs based on a predetermined mappingrule, wherein K is a value less than 168. Therefore, the PSSID may havea value in a range from 0 to 167 or in a range from 0 to K-1. The PSSIDmay be expressed as N_(ID) ^(D2D)=N_(ID) ⁽¹⁾, and N_(ID) ⁽¹⁾ associatedwith an SD2DSS may be mapped in one-to-one correspondences to an SSShaving 168 sequences, or may be mapped to K sequences based on sequencesmodified or partially selected from the SSS having 168 sequences,wherein K is a value less than 168. When N_(ID) ⁽¹⁾ is mapped inone-to-one correspondence to 168 sequences, it may have an integer valuein a range from 0 to 167, and when it is mapped in one-to-onecorrespondence to K sequences, it may have an integer in a range from 0to K-1. In this instance, an accurate UE ID of the transmissionsynchronization source may be transmitted through a PD2DSCH.

FIG. 3 is a conceptual diagram of a system to which a method oftransmitting a synchronization signal is applied according to one ormore exemplary embodiments.

The upper portion of FIG. 3 illustrates synchronization signaltransmissions executed from an eNodeB 300 to a first UE 310, from thefirst UE 310 to a second UE 320, from the second UE 320 to a third UE330, and from the third UE 330 to a fourth UE 340, respectively. Thebase station 300 may be an original Synchronization Source (original SS)for the first UE 310, the second UE 320, the third UE 330, and thefourth UE 340. The base station 300 may be a transmissionsynchronization source (Tx SS) for the first UE 310, the first UE 310may be a Tx SS for the second UE 320, the second UE 320 may be a Tx SSfor the third UE 330, the third UE 330 may be a Tx SS for the fourth UE340.

Referring to the lower portion of FIG. 3, a fifth UE 350 may not receivea synchronization signal from an eNodeB or another UE, but generate asynchronization signal by itself and transmit the same, and thus, thefifth UE 350 corresponds to an ISS. The fifth UE 350 may transmit asynchronization signal to a sixth UE 360, and the sixth UE 360 transmitsa synchronization signal to a seventh UE 370, and the seventh UE 370transmits a synchronization signal to an eighth UE 380. The fifth UE 350may be an original Synchronization Source (original SS) for the sixth UE360, the seventh UE 370, and the eighth UE 380. The fifth UE 350 may bea transmission synchronization source (Tx SS) for the sixth UE 360, thesixth UE 360 may be a Tx SS for the seventh UE 370, and the seventh UE370 may be a Tx SS for the eighth UE 380.

Embodiments 2-1 to 2-5 describe a method of indicating D2Dsynchronization information when the maximum stratum level is a fourthstratum (the maximum stratum level is a third stratum when the eNodeB isexcluded) in the case where an original synchronization source is aneNodeB, and when the maximum stratum level is a third stratum in thecase where the original synchronization source is an ISS.

[Embodiment 2-1]

TABLE 10 Type of SS Stratum level Case Tx SS Original SS PSSID (hopcount) Case 1: eNodeB→UE₁ eNodeB PCID of Index 0 eNodeB eNodeB eNodeB(or not defined) Case 2: eNodeB→UE₁→UE₂ SS relaying eNodeB PCID of Index1 UE (=UE₁) eNodeB eNodeB Case 3: eNodeB→UE₁→UE₂→UE₃ SS relaying eNodeBPCID of Index 2 UE (=UE₂) eNodeB eNodeB Case 4: SS relaying eNodeB PCIDof Index 3 eNodeB→UE₁→UE₂→UE₃→UE₄ UE (=UE₃) eNodeB eNodeB Case 5: ISS(=UE_(A))→UE_(B) ISS Based on Index 1 UE (=UE_(A)) ISS (=UE_(A)) ISS(=UE_(A)) ID Case 6: ISS (=UE_(A))→UE_(B)→UE_(C) SS relaying ISS Basedon Index 2 UE (=UE_(B)) ISS (=UE_(A)) ISS (=UE_(A)) ID Case 7: SSrelaying ISS Based on Index 3 ISS (=UE_(A))→UE_(B)→UE_(C)→UE_(D) UE(=UE_(C)) ISS (=UE_(A)) ISS (=UE_(A)) ID

In the present embodiment, when a type of a Synchronization Source (SS)is an eNodeB or an SS derived from an eNodeB (SS relaying eNodeB), aPCID of an eNodeB may be used as a Physical Synchronization SourceIdentity (PSSID), and 504 unique PSSIDs may exist.

When a type of a Synchronization Source (SS) is an ISS or an SS derivedfrom an ISS (an SS relaying an ISS), a PSSID based on a UE ID of an ISSmay be used and 504 unique PSSIDs may exist.

In the present embodiment, a type of a transmission synchronizationsource may be indicated by a root index value of a PD2DSS. For example,cases of Table 10 may be classified into two cases, that is, a casecorresponding to Case 1 in which a transmission synchronization sourceis an eNodeB and the other case corresponding to Cases 2 to 7 in which atransmission synchronization source is a UE, and each case may beindicated by a root index value of a PD2DSS. A PD2DSS when thetransmission synchronization source is an eNodeB, may use 25, 29, and34, which are identical to the root indices of a PSS A PD2DSS when thetransmission synchronization source is a UE may use newly defined rootindices which are different from the root indices of a PSS. For example,the root indices of Table 4 may be used.

When the transmission synchronization source is a UE, a type of anoriginal synchronization source may be indicated by a Physical D2DSynchronization Channel (PD2DSCH). For example, the cases of Table 10may be indicated based on the classification into two cases, that is, acase corresponding to Cases 2 to 4 in which a type of an originalsynchronization source is an eNodeB and a case corresponding to Cases 5to 7 in which a type of an original synchronization source is anIndependent Synchronization Source (ISS). Therefore, an indication valueof the PD2DSCH may have a one-bit value. When the transmissionsynchronization source is an eNodeB, it may be recognized that theoriginal synchronization source is the eNodeB, through a root indexvalue of the PD2DSS, and thus, this may not need to be indicatedseparately.

In addition, when the transmission synchronization source is a UE, astratum level may be indicated by a location where a D2DSS istransmitted in a frequency-resource domain or a PD2DSCH. For example,cases 2 to 7 of Table 10 may be indicated based on the classificationinto three cases, that is, a case corresponding to Cases 2 and 5 inwhich a stratum level index is 1, another case corresponding to Cases 3and 6 in which a stratum level index is 2, and the other casecorresponding to Cases 4 and 7 in which a stratum level index is 3.Therefore, an indication value of the PD2DSCH may have a 2-bit value.When the transmission synchronization source is an eNodeB, it isrecognized that the stratum level has 0 through the PD2DSS and thus,this may not need to be indicated separately.

When a type of the synchronization source is an eNodeB, a physical layercell ID (N_(ID) ^(cell)) corresponding to a PCID of the eNodeB may beused as a Physical Synchronization Source Identity (PSSID). The physicallayer cell ID may be expressed as N_(ID) ^(cell)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾,and N_(ID) ⁽²⁾ may be mapped in one-to-one correspondence to rootindices of the PD2DSS that may have three values, and may have aninteger in a range from 0 to 2. In this instance, the root index of thePD2DSS may have one of 25, 29, and 34, which are identical to the rootindices of the PSS. N_(ID) ⁽¹⁾ may be mapped in one-to-onecorrespondence to root indices of an SD2DSS that may have 168 values,and may have an integer in a range from 0 to 167. In this instance, avalue that is identical to the SSS may be used as the value of theSD2DSS.

Even when the type of the synchronization source is a synchronizationsource derived from an eNodeB (Cases 2, 3, and 4), a PhysicalSynchronization Source Identity (PSSID) may have a value identical tothe PCID of the eNodeB, and 504 unique PSSIDs may exist. The PSSID maybe expressed as N_(ID) ^(D2D)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾, and N_(ID) ⁽²⁾ maybe mapped in one-to-one correspondence to root indices of the PD2DSSthat may have three values, and may have an integer in a range from 0 to2. In this instance, newly defined root indices which are different fromthe root indices of the PSS may be used as a root index of the PD2DSS,and for example, the root indices of Table 4 may be used. For N_(ID)⁽¹⁾, a value of an SD2DSS that is mapped in one-to-one correspondence toan SSS having 168 sequences may be used. Therefore, the SD2DSS may havean integer in a range from 0 to 167, and a PSSID may be mapped to504(=3*168) IDs.

When the type of the synchronization source is an ISS or asynchronization source derived from an ISS (Cases 5, 6, and 7), aProximity based Services (ProSe) UE ID of a UE corresponding to the ISSmay be used as a Physical Synchronization Source Identity (PSSID), andthe PSSID may be mapped to 504 IDs based on a predetermined mappingrule. The PSSID may be expressed as N_(ID) ^(D2D)=3N_(ID) ⁽¹⁾+N_(ID)⁽²⁾, and N_(ID) ⁽²⁾ may be mapped in one-to-one correspondence to rootindices of the PD2DSS that may have three values, and may have aninteger in a range from 0 to 2. In this instance, newly defined rootindices which are different from the root indices of the PSS may be usedas a root index of the PD2DSS, and for example, the root indices ofTable 4 may be used. N_(ID) ⁽¹⁾ associated with the SD2DSS may be mappedin one-to-one correspondence to an SSS having 168 sequences and may havean integer in a range from 0 to 167. Therefore, the PSSID may be mappedto 504(=3*168) IDs.

[Embodiment 2-2]

TABLE 11 Type of SS Stratum level Case Tx SS Original SS PSSID (hopcount) Case 1: eNodeB→UE₁ eNodeB PCID of Index 0 eNodeB eNodeB eNodeB(or not defined) Case 2: eNodeB→UE₁→UE₂ SS relaying eNodeB Based onIndex 1 UE (=UE₁) eNodeB PCID of eNodeB Case 3: eNodeB→UE₁→UE₂→UE₃ SSrelaying eNodeB Based on Index 2 UE (=UE₂) eNodeB PCID of eNodeB Case 4:SS relaying eNodeB Based on Index 3 eNodeB→UE₁→UE₂→UE₃→UE₄ UE (=UE₃)eNodeB PCID of eNodeB Case 5: ISS (=UE_(A))→UE_(B) ISS Based on Index 1UE (=UE_(A)) ISS (=UE_(A)) ISS (=UE_(A)) ID Case 6: ISS(=UE_(A))→UE_(B)→UE_(C) SS relaying ISS Based on Index 2 UE (=UE_(B))ISS (=UE_(A)) ISS (=UE_(A)) ID Case 7: SS relaying ISS Based on Index 3ISS (=UE_(A))→UE_(B)→UE_(C)→UE_(D) UE (=UE_(C)) ISS (=UE_(A)) ISS(=UE_(A)) ID

In the present embodiment, when a type of a Synchronization Source (SS)is an eNodeB, a PCID of the eNodeB may be used as a PSSID, and 504unique PSSIDs may be used. When the type of the synchronization sourceis an Synchronization Source (SS) derived from an eNodeB (SS relaying aneNodeB), a value modified based on the PCID of the eNodeB may be used asa PSSID, and 168 or K unique PSSIDs may exist, wherein K is a value thatis less than 168.

When the type of the Synchronization Source (SS) is an ISS or an SSderived from an ISS (an SS relaying an ISS), a PSSID may be determinedbased on a UE ID of the ISS, and 168 or K unique PSSIDs may exist,wherein K is a value that is less than 168.

In the present embodiment, a type of a transmission synchronizationsource may be indicated by a root index value of a PD2DSS. For example,cases of Table 11 may be classified into two cases, that is, a casecorresponding to Case 1 in which a transmission synchronization sourceis an eNodeB and the other case corresponding to Cases 2 to 7 in which atransmission synchronization source is a UE, and each case may beindicated by a root index value of a PD2DSS. A PD2DSS when thetransmission synchronization source is an eNodeB, may use 25, 29, and34, which are identical to the root indices of a PSS A PD2DSS when thetransmission synchronization source is a UE may use newly defined rootindices which are different from the root indices of a PSS. For example,the root indices of Table 4 may be used.

When the transmission synchronization source is a UE, a type of anoriginal synchronization source may be indicated by a Physical D2DSynchronization Channel (PD2DSCH). For example, the cases of Table 11may be indicated based on the classification into two cases, that is, acase corresponding to Cases 2 to 4 in which a type of an originalsynchronization source is an eNodeB and the other case corresponding toCases 5 to 7 in which a type of an original synchronization source is anIndependent Synchronization Source (ISS). Therefore, an indication valueof the PD2DSCH may have a one-bit value. When the transmissionsynchronization source is an eNodeB, it may be recognized that theoriginal synchronization source is the eNodeB, through a root indexvalue of the PD2DSS, and thus, this may not need to be indicatedseparately.

When the transmission synchronization source is a UE, a stratum levelmay be indicated by a root index of a PD2DSS. For example, cases ofTable 11 may be indicated based on the classification into three cases,that is, a case corresponding to Cases 2 and 5 in which a stratum levelindex is 1, another case corresponding to Cases 3 and 6 in which astratum level index is 2, and the other case corresponding to Cases 4and 7 in which a stratum level index is 3. Therefore, when three newlydefined root indices of a PD2DSS are X, Y, and Z, respectively, forexample, a root index X may be set to indicate a stratum level 1, a rootindex Y may be set to indicate a stratum level 2, and a root index Z maybe set to indicate a stratum level 3. The root indices of Table 4 may beused as the newly defined root indices of the PD2DSS.

When the type of the synchronization source is an eNodeB (Case 1), aphysical layer cell ID (N_(ID) ^(cell)) corresponding to a PCID of theeNodeB may be used as a Physical Synchronization Source Identity(PSSID). The physical layer cell ID may be expressed as N_(ID)^(cell)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾, and N_(ID) ⁽²⁾ may be mapped inone-to-one correspondence to root indices of the PD2DSS that may havethree values, and may have an integer in a range from 0 to 2. In thisinstance, the root index of the PD2DSS may have one of 25, 29, and 34,which are identical to the root indices of the PSS. N_(ID) ⁽¹⁾ may bemapped in one-to-one correspondence to root indices of an SD2DSS thatmay have 168 values, and may have an integer in a range from 0 to 167.In this instance, a value that is identical to the SSS may be used asthe value of the SD2DSS.

When the type of the synchronization source is a synchronization sourcederived from an eNodeB (an SS relaying an eNodeB) (Cases 2, 3, and 4), aPhysical Synchronization Source Identity (PSSID) may be mapped to 168 orK IDs based on a PCID of the eNodeB using a predetermined rule, whereinK is a value that is less than 168. Therefore, the PSSID may have avalue in a range from 0 to 167 or in a range from 0 to K-1. The PSSIDmay be expressed as N_(ID) ^(D2D)=N_(ID) ⁽¹⁾, and N_(ID) ⁽¹⁾ associatedwith the SD2DSS may be mapped in one-to-one correspondence to an SSSthat may have 168 values, and may have an integer in a range from 0 to167, or may be mapped in one-to-one correspondence to K values, based onsequences that are modified or partially selected from an SSS having 168sequences and may have an integer in a range from 0 to K-1, wherein K isa value less than 168. In this instance, an accurate PCID of the eNodeBmay be transmitted through a PD2DSCH.

When the type of the synchronization source is an ISS or asynchronization source derived from an ISS (an SS relaying an ISS)(Cases 5, 6, and 7), a Proximity based Services (ProSe) UE ID of a UEcorresponding to the ISS may be used as a Physical SynchronizationSource Identity (PSSID), and the PSSID may be mapped to 168 or K IDsbased on a predetermined mapping rule, wherein K is a value that is lessthan 168. Therefore, the PSSID may have a value in a range from 0 to 167or in a range from 0 to K-1. The PSSID may be expressed as N_(ID)^(D2D)=N_(ID) ⁽¹⁾, and N_(ID) ⁽¹⁾ associated with the SD2DSS may bemapped in one-to-one correspondence to an SSS that may have 168 values,and may have an integer in a range from 0 to 167, or may be mapped inone-to-one correspondence to K values, based on sequences that aremodified or partially selected from an SSS having 168 sequences and mayhave an integer in a range from 0 to K-1, wherein K is a value less than168. Therefore, the PSSID may have a value in a range from 0 to 167 orin a range from 0 to K-1. In this instance, an accurate PCID of the ISSmay be transmitted through a PD2DSCH.

[Embodiment 2-3]

TABLE 12 Type of SS Stratum level Case Tx SS Original SS PSSID (hopcount) Case 1: eNodeB→UE₁ eNodeB PCID of Index 0 eNodeB eNodeB eNodeB(or not defined) Case 2: eNodeB→UE₁→UE₂ SS relaying eNodeB PCID of Index1 UE (=UE₁) eNodeB eNodeB Case 3: eNodeB→UE₁→UE₂→UE₃ SS relaying eNodeBPCID of Index 2 UE (=UE₂) eNodeB eNodeB Case 4: SS relaying eNodeB PCIDof Index 3 eNodeB→UE₁→UE₂→UE₃→UE₄ UE (=UE₃) eNodeB eNodeB Case 5: ISS(=UE_(A))→UE_(B) ISS Based on Index 1 UE (=UE_(A)) ISS (=UE_(A)) ISS(=UE_(A)) ID Case 6: ISS (=UE_(A))→UE_(B)→UE_(C) SS relaying ISS Basedon Index 2 UE (=UE_(B)) ISS (=UE_(A)) ISS (=UE_(A)) ID Case 7: SSrelaying ISS Based on Index 3 ISS (=UE_(A))→UE_(B)→UE_(C)→UE_(D) UE(=UE_(C)) ISS (=UE_(A)) ISS (=UE_(A)) ID

In the present embodiment, when a type of a Synchronization Source (SS)is an eNodeB or an SS derived from an eNodeB (an SS relaying an eNodeB),a PCID of the eNodeB may be used as a PSSID, and 504 unique PSSIDs maybe used.

When the type of the Synchronization Source (SS) is an ISS or an SSderived from an ISS (an SS relaying an ISS), a PSSID may be determinedbased on an ISS ID, and 168 or K unique PSSIDs may exist, wherein K is avalue that is less than 168.

In the present embodiment, a type of a transmission synchronizationsource may be indicated by a root index value of a PD2DSS. For example,cases of Table 12 may be classified into two cases, that is, a casecorresponding to Case 1 in which a transmission synchronization sourceis an eNodeB and the other case corresponding to Cases 2 to 7 in which atransmission synchronization source is a UE, and each case may beindicated by a root index value of a PD2DSS. A PD2DSS when thetransmission synchronization source is an eNodeB, may use 25, 29, and34, which are identical to the root indices of a PSS A PD2DSS when thetransmission synchronization source is a UE may use newly defined rootindices which are different from the root indices of a PSS. For example,the root indices of Table 4 may be used.

When the transmission synchronization source is a UE, a type of anoriginal synchronization source may be indicated by a Physical D2DSynchronization Channel (PD2DSCH). For example, the cases of Table 12may be indicated based on the classification into two cases, that is, acase corresponding to Cases 2 to 4 in which a type of an originalsynchronization source is an eNodeB and the other case corresponding toCases 5 to 7 in which a type of an original synchronization source is anIndependent Synchronization Source (ISS). Therefore, an indication valueof the PD2DSCH may have a one-bit value. When the transmissionsynchronization source is an eNodeB, it may be recognized that theoriginal synchronization source is the eNodeB, through a root indexvalue of the PD2DSS, and thus, this may not need to be indicatedseparately.

In addition, when the original synchronization source is an eNodeB andthe transmission synchronization source is a UE, a stratum level may beindicated by a location where a D2DSS is transmitted in afrequency-resource domain or a PD2DSCH. For example, the cases of Table12 may be indicated based on the classification into three cases, thatis, a case corresponding to Case 2 in which a stratum level is 1,another case corresponding to Case 3 in which a stratum level is 2, andthe other case corresponding to Case 4 in which a stratum level is 3.Therefore, an indication value of the PD2DSCH may have a 2-bit value.Here, 2-bit information of the PD2DSCH may be designed to be differentbased on a coverage scenario, and the 2-bit information of the PD2DSCHmay be designed to not be included in an out-of-coverage. Therefore, inCases 5 and 6 in which the original synchronization source is an ISS, astratum level may be indicated by a root index value of a PD2DSS, asopposed to by a PD2DSH. When the transmission synchronization source isan eNodeB, a stratum level may be recognized through a root index valueof the PD2DSS, and thus, this may not need to be indicated separately.

When the original synchronization source is an ISS, a stratum level maybe indicated by a root index of a PD2DSS. Cases 5 and 6 of Table 12 maybe classified into a total of three cases, based on a stratum level.Therefore, when three newly defined root indices of a PD2DSS are X, Y,and Z, respectively, for example, a root index X may be set to indicatea stratum level 1, a root index Y may be set to indicate a stratum level2, and a root index Z may be set to indicate a stratum level 3. The rootindices of Table 4 may be used as the newly defined root indices of thePD2DSS.

When the type of the synchronization source is an eNodeB (Case 1), aphysical layer cell ID (N_(ID) ^(cell)) corresponding to a PCID of theeNodeB may be used as a Physical Synchronization Source Identity(PSSID). The physical layer cell ID may be expressed as N_(ID)^(cell)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾, and N_(ID) ⁽²⁾ may be mapped inone-to-one correspondence to root indices of the PD2DSS that may havethree values, and may have an integer in a range from 0 to 2. In thisinstance, the root index of the PD2DSS may have one of 25, 29, and 34,which are identical to the root indices of the PSS. N_(ID) ⁽¹⁾ may bemapped in one-to-one correspondence to root indices of an SD2DSS thatmay have 168 values, and may have an integer in a range from 0 to 167.In this instance, a value that is identical to the SSS may be used asthe value of the SD2DSS.

Even when the type of the synchronization source is a synchronizationsource derived from an eNodeB (Cases 2, 3, and 4), a PhysicalSynchronization Source Identity (PSSID) may have a value identical tothe PCID of the eNodeB, and 504 unique PSSIDs may exist. The PSSID maybe expressed as N_(ID) ^(D2D)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾, and N_(ID) ⁽²⁾ maybe mapped in one-to-one correspondence to root indices of the PD2DSSthat may have three values, and may have an integer in a range from 0 to2. In this instance, newly defined root indices which are different fromthe root indices of the PSS may be used as a root index of the PD2DSS,and for example, the root indices of Table 4 may be used. For N_(ID)⁽¹⁾, a value of an SD2DSS that is mapped in one-to-one correspondence toan SSS having 168 sequences may be used. Therefore, the SD2DSS may havean integer in a range from 0 to 167, and a PSSID may be mapped to504(=3*168) IDs.

When the type of the synchronization source is an ISS or asynchronization source derived from an ISS (SS relaying an ISS) (Cases5, 6, and 7), a Proximity based Services (ProSe) UE ID of a UEcorresponding to the ISS may be used as a Physical SynchronizationSource Identity (PSSID), and the PSSID may be mapped to 168 or K IDsbased on a predetermined mapping rule, wherein K is a value that is lessthan 168. Therefore, the PSSID may have a value in a range from 0 to 167or in a range from 0 to K-1. The PSSID may be expressed as N_(ID)^(D2D)=N_(ID) ⁽¹⁾, and N_(ID) ⁽¹⁾ associated with the SD2DSS may bemapped in one-to-one correspondence to an SSS that may have 168 values,and may have an integer in a range from 0 to 167, or may be mapped inone-to-one correspondence to K values, based on sequences that aremodified or partially selected from an SSS having 168 sequences and mayhave an integer in a range from 0 to K-1, wherein K is a value less than168. In this instance, an accurate UE ID of the ISS may be transmittedthrough a PD2DSCH.

[Embodiment 2-4]

TABLE 13 Type of SS Stratum level Case Tx SS Original SS PSSID (hopcount) Case 1: eNodeB→UE₁ eNodeB PCID of Index 0 eNodeB eNodeB eNodeB(or not defined) Case 2: eNodeB→UE₁→UE₂ SS relaying eNodeB Based onIndex 1 UE (=UE₁) eNodeB UE (=UE₁) ID Case 3: eNodeB→UE₁→UE₂→UE₃ SSrelaying eNodeB Based on Index 2 UE (=UE₂) eNodeB UE (=UE₂) ID Case 4:SS relaying eNodeB Based on Index 3 eNodeB→UE₁→UE₂→UE₃→UE₄ UE (=UE₃)eNodeB UE (=UE₃) ID Case 5: ISS (=UE_(A))→UE_(B) ISS Based on Index 1 UE(=UE_(A)) ISS (=UE_(A)) UE (=UE_(A)) ID Case 6: ISS(=UE_(A))→UE_(B)→UE_(C) SS relaying ISS Based on Index 2 UE (=UE_(B))ISS (=UE_(A)) UE (=UE_(B)) ID Case 7: SS relaying ISS Based on Index 3ISS (=UE_(A))→UE_(B)→UE_(C)→UE_(D) UE (=UE_(C)) ISS (=UE_(A)) UE(=UE_(C)) ID

In the present embodiment, when a type of a Synchronization Source (SS)is an eNodeB, a PCID of the eNodeB may be used as a PSSID, and 504unique PSSIDs may be used.

When the type of the Synchronization Source (SS) is an SS derived froman eNodeB (an SS relaying an eNodeB), an ISS, or an SS derived from anISS (an SS relaying an ISS), a PSSID may be determined based on a UE IDof a transmission synchronization source, and 504 unique PSSIDs mayexist.

In the present embodiment, a type of a transmission synchronizationsource may be indicated by a root index value of a PD2DSS. For example,cases of Table 13 may be classified into two cases, that is, a casecorresponding to Case 1 in which a transmission synchronization sourceis an eNodeB and the other case corresponding to Cases 2 to 7 in which atransmission synchronization source is a UE, and each case may beindicated by a root index value of a PD2DSS. A PD2DSS when thetransmission synchronization source is an eNodeB, may use 25, 29, and34, which are identical to the root indices of a PSS A PD2DSS when thetransmission synchronization source is a UE may use newly defined rootindices which are different from the root indices of a PSS. For example,the root indices of Table 4 may be used.

When the transmission synchronization source is a UE, a type of anoriginal synchronization source may be indicated by a Physical D2DSynchronization Channel (PD2DSCH). For example, the cases of Table 13may be indicated based on the classification into two cases, that is, acase corresponding to Cases 2 to 4 in which a type of an originalsynchronization source is an eNodeB and a case corresponding to Cases 5to 7 in which a type of an original synchronization source is anIndependent Synchronization Source (ISS). Therefore, an indication valueof the PD2DSCH may have a one-bit value. When the transmissionsynchronization source is an eNodeB, it may be recognized that theoriginal synchronization source is the eNodeB, through a root indexvalue of the PD2DSS, and thus, this may not need to be indicatedseparately.

In addition, when the transmission synchronization source is a UE, astratum level may be indicated by a location where a D2DSS istransmitted in a frequency-resource domain or a PD2DSCH. For example,the cases of Table 13 may be indicated based on the classification intothree cases, that is, a case corresponding to Cases 2 and 5 in which astratum level index is 1, another case corresponding to Cases 3 and 6 inwhich a stratum level index is 2, and the other case corresponding toCases 4 and 7 in which a stratum level index is 3. Therefore, anindication value of the PD2DSCH may have a 2-bit value.

When the type of the synchronization source is an eNodeB (Case 1), aphysical layer cell ID (N_(ID) ^(cell)) corresponding to a PCID of theeNodeB may be used as a Physical Synchronization Source Identity(PSSID). The physical layer cell ID may be expressed as N_(ID)^(cell)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾, and N_(ID) ⁽²⁾ may be mapped inone-to-one correspondence to root indices of the PD2DSS that may havethree values, and may have an integer in a range from 0 to 2. In thisinstance, the root index of the PD2DSS may have one of 25, 29, and 34,which are identical to the root indices of the PSS. N_(ID) ⁽¹⁾ may bemapped in one-to-one correspondence to root indices of an SD2DSS thatmay have 168 values, and may have an integer in a range from 0 to 167.In this instance, a value that is identical to the SSS may be used asthe value of the SD2DSS.

When the type of the synchronization source is a synchronization sourcederived from an eNodeB (an SS relaying an eNodeB), an ISS, or asynchronization source derived from an ISS (an SS relaying an ISS)(Cases 2, 3, 4, 5, 6, and 7), a Proximity based Services (ProSe) UE IDof a transmission (Tx) UE may be used as a Physical SynchronizationSource Identity (PSSID), and the PSSID may be mapped to 504 IDs based ona predetermined mapping rule. The PSSID may be expressed as N_(ID)^(D2D)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾, and N_(ID) ⁽²⁾ may be mapped inone-to-one correspondence to root indices of the PD2DSS that may havethree values, and may have an integer in a range from 0 to 2. In thisinstance, newly defined root indices which are different from the rootindices of the PSS may be used as a root index of the PD2DSS, and forexample, the root indices of Table 4 may be used. N_(ID) ⁽¹⁾ associatedwith the SD2DSS may be mapped in one-to-one correspondence to an SSShaving 168 sequences and may have an integer in a range from 0 to 167.Therefore, the PSSID may be mapped to 504(=3*168) IDs.

[Embodiment 2-5]

TABLE 14 Type of SS Stratum level Case Tx SS Oritinal SS PSSID (hopcount) Case 1: eNodeB→UE₁ eNodeB PCID of Index 0 eNodeB eNodeB eNodeB(or not defined) Case 2: eNodeB→UE₁→UE₂ SS relaying eNodeB Based onIndex 1 UE (=UE₁) eNodeB UE (=UE₁) ID Case 3: eNodeB→UE₁→UE₂→UE₃ SSrelaying eNodeB Based on Index 2 UE (=UE₂) eNodeB UE (=UE₂) ID Case 4:SS relaying eNodeB Based on Index 3 eNodeB→UE₁→UE₂→UE₃→UE₄ UE (=UE₃)eNodeB UE (=UE₃) ID Case 5: ISS(=UE_(A))→UE_(B) ISS Based on Index 1 UE(=UE_(A)) ISS (=UE_(A)) UE (=UE_(A)) ID Case 6: ISS(=UE_(A))→UE_(B)→UE_(C) SS relaying ISS Based on Index 2 UE (=UE_(B))ISS (=UE_(A)) UE (=UE_(B)) ID Case 7: SS relaying ISS Based on Index 3ISS (=UE_(A))→UE_(B)→UE_(C)→UE_(D) UE (=UE_(C)) ISS (=UE_(A)) UE(=UE_(C)) ID

In the present embodiment, when a type of a Synchronization Source (SS)is an eNodeB, a PCID of the eNodeB may be used as a PhysicalSynchronization Source Identity (PSSID), and 504 unique PSSIDs mayexist.

When the type of the Synchronization Source (SS) is an SS derived froman eNodeB (an SS relaying an eNodeB), an ISS, or an SS derived from anISS (an SS relaying an ISS), a PSSID based on a UE ID of a transmissionsynchronization source may be used as a PSSID, and 168 or K uniquePSSIDs may exist, wherein K is a value less than 168.

In the present embodiment, a type of a transmission synchronizationsource may be indicated by a root index value of a PD2DSS. For example,the cases of Table 14 may be classified into two cases, that is, a casecorresponding to Case 1 in which a transmission synchronization sourceis an eNodeB and the other case corresponding to Cases 2 to 7 in which atransmission synchronization source is a UE, and each case may beindicated by a root index value of a PD2DSS. A PD2DSS when thetransmission synchronization source is an eNodeB, may use 25, 29, and34, which are identical to the root indices of a PSS A PD2DSS when thetransmission synchronization source is a UE may use newly defined rootindices which are different from the root indices of a PSS. For example,the root indices of Table 4 may be used.

When the transmission synchronization source is a UE, a type of anoriginal synchronization source may be indicated by a Physical D2DSynchronization Channel (PD2DSCH). For example, the cases of Table 14may be indicated based on the classification into two cases, that is, acase corresponding to Cases 2 to 4 in which a type of an originalsynchronization source is an eNodeB and the other case corresponding toCases 5 to 7 in which a type of an original synchronization source is anIndependent Synchronization Source (ISS). Therefore, an indication valueof the PD2DSCH may have a one-bit value. When the transmissionsynchronization source is an eNodeB, it may be recognized that theoriginal synchronization source is the eNodeB, through a root indexvalue of the PD2DSS, and thus, this may not need to be indicatedseparately.

When the transmission synchronization source is an eNodeB, a stratumlevel only has an index value of 0. Also, the stratum level may beindicated by any one of 25, 29, and 34, which are root indices of thePD2DSS.

When the transmission synchronization source is a UE, a stratum levelmay be indicated by a root index of a PD2DSS. For example, the cases ofTable 14 may be indicated based on the classification into three cases,that is, a case corresponding to Cases 2 and 5 in which a stratum levelindex is 1, another case corresponding to Cases 3 and 6 in which astratum level index is 2, and the other case corresponding to Cases 4and 7 in which a stratum level index is 3. Therefore, when three newlydefined root indices of a PD2DSS are X, Y, and Z, respectively, forexample, a root index X may be set to indicate a stratum level 1, a rootindex Y may be set to indicate a stratum level 2, and a root index Z maybe set to indicate a stratum level 3. The root indices of Table 4 may beused as the newly defined root indices of the PD2DSS.

When the type of the synchronization source is an eNodeB, a physicallayer cell ID (N_(ID) ^(cell)) corresponding to a PCID of the eNodeB maybe used as a Physical Synchronization Source Identity (PSSID). Thephysical layer cell ID may be expressed as N_(ID) ^(cell)=3N_(ID)⁽¹⁾+N_(ID) ⁽²⁾, and N_(ID) ⁽²⁾ may be mapped in one-to-onecorrespondence to root indices of the PD2DSS that may have three values,and may have an integer in a range from 0 to 2. In this instance, theroot index of the PD2DSS may have one of 25, 29, and 34, which areidentical to the root indices of the PSS. N_(ID) ⁽¹⁾ may be mapped inone-to-one correspondence to root indices of an SD2DSS that may have 168values, and may have an integer in a range from 0 to 167. In thisinstance, a value that is identical to the SSS may be used as the valueof the SD2DSS.

When the type of the synchronization source is a synchronization sourcederived from an eNodeB (an SS relaying an eNodeB), an ISS, or asynchronization source derived from an ISS (an SS relaying an ISS), aProximity based Services (ProSe) UE ID of a transmission (Tx) UE may beused as a Physical Synchronization Source Identity (PSSID), and thePSSID may be mapped to 168 or K IDs based on a predetermined mappingrule, wherein K is a value less than 168. Therefore, the PSSID may havea value in a range from 0 to 167 or in a range from 0 to K-1. The PSSIDmay be expressed by N_(ID) ^(D2D)=N_(ID) ⁽¹⁾, and N_(ID) ⁽¹⁾ associatedwith the SD2DSS may be mapped in one-to-one correspondences to an SSShaving 168 sequences, or may be mapped to K sequences based on sequencesmodified or partially selected from the SSS having 168 sequences,wherein K is a value less than 168. When N_(ID) ⁽¹⁾ is mapped inone-to-one correspondence to 168 sequences, it may have an integer in arange from 0 to 167, and when it is mapped in one-to-one correspondenceto K sequences, it may have an integer in a range from 0 to K-1. In thisinstance, an accurate UE ID of the transmission synchronization sourcemay be transmitted through a PD2DSCH.

FIG. 4 is a conceptual diagram of a system to which a method oftransmitting a synchronization signal is applied according to one ormore exemplary embodiments.

The upper portion of FIG. 4 illustrates synchronization signaltransmissions executed from an eNodeB 400 to a first UE 410, from thefirst UE 410 to a second UE 420, and from the second UE 420 to a thirdUE 430, respectively. The eNodeB 400 may be an original SynchronizationSource (original SS) for the first UE 410, the second UE 420, and thethird UE 430. The eNodeB 400 may be a transmission synchronizationsource (Tx SS) for the first UE 410, the first UE 410 may be a Tx SS forthe second UE 420, and the second UE 420 may be a Tx SS for the third UE430.

Referring to the lower portion of FIG. 4, a fourth UE 440 may notreceive a synchronization signal from an eNodeB or another UE, butgenerate a synchronization signal by itself and transmit the same, andthus, the fourth UE 440 corresponds to an ISS. The fourth UE 440 maytransmit a direct synchronization signal to the fifth UE 450. Therefore,the fourth UE 440 may be both an original synchronization source(original SS) and a transmission synchronization source (Tx SS), withrespect to the fifth UE 450. In FIG. 4, UEs may exist between the fourthUE 440 and the fifth UE 450, the fourth UE 440 transmits a directsynchronization signal to one of the UEs, and a UE that takes the fourthUE 440 as an original synchronization source from among the UEs maytransmit a direct synchronization signal to the fifth UE 450. Even inthis instance, that is, even though the synchronization of the fourth UE440, which is the original synchronization source, is transmitted to thefifth UE 450 via a few UEs, the fifth UE 450 assumes a first stratumlevel as a stratum level. In other words, when the originalsynchronization source is an ISS, a stratum level is assumed to be anidentical value or may not be defined.

Embodiments 3-1 to 3-5 describe a method of indicating D2Dsynchronization information when the maximum stratum level is a thirdstratum (the maximum stratum level is a second stratum when the eNodeBis excluded) in the case where an original synchronization source is aneNodeB, and when the maximum stratum level is a first stratum (or notdefined) in the case where the original synchronization source is anISS.

[Embodiment 3-1]

TABLE 15 Type of SS Stratum level Case Tx SS Original SS PSSID (hopcount) Case 1: eNodeB→UE₁ eNodeB PCID of 1^(st) eNodeB eNodeB eNodeB(Index 0 (or 1)) Case 2: eNodeB→UE₁→UE₂ SS relaying eNodeB PCID of2^(nd) UE (=UE₁) eNodeB eNodeB (Index 1 (or 2)) Case 3: SS relayingeNodeB PCID of 3^(rd) eNodeB→UE₁→UE₂→UE₃ UE (=UE₂) eNodeB eNodeB (Index2 (or 3)) Case 4: ISS (=UE_(A))→ . . . →UE_(B) ISS or SS relaying ISSBased on 1^(st) UE (e.g. UE_(A)) ISS (=UE_(A)) ISS (=UE_(A)) ID (Index 0(or 1))(or not defined)

In the present embodiment, when a type of a Synchronization Source (SS)is an eNodeB or an SS derived from an eNodeB (SS relaying eNodeB), aPCID of an eNodeB may be used as a Physical Synchronization SourceIdentity (PSSID), and 504 unique PSSIDs may exist.

When a type of a Synchronization Source (SS) is an ISS or an SS derivedfrom an ISS (an SS relaying an ISS), a PSSID based on a UE ID of an ISSmay be used as a PSSID, and 504 unique PSSIDs may exist.

In the present embodiment, a type of a transmission synchronizationsource may be indicated by a root index value of a PD2DSS. For example,the cases of Table 15 may be classified into two cases, that is, a casecorresponding to Case 1 in which a transmission synchronization sourceis an eNodeB and the other case corresponding to Cases 2 to 4 in which atransmission synchronization source is a UE, and each case may beindicated by a root index value of a PD2DSS. A PD2DSS when thetransmission synchronization source is an eNodeB, may use 25, 29, and34, which are identical to the root indices of a PSS A PD2DSS when thetransmission synchronization source is a UE, may use newly defined rootindices which are different from the root indices of a PSS. For example,the root indices of Table 4 may be used.

When the transmission synchronization source is a UE, a type of anoriginal synchronization source may be indicated by a Physical D2DSynchronization Channel (PD2DSCH). For example, the cases of Table 15may be indicated based on the classification into two cases, that is, acase corresponding to Cases 2 and 3 in which a type of an originalsynchronization source is an eNodeB and the other case corresponding toCase 4 in which a type of an original synchronization source is anIndependent Synchronization Source (ISS). Therefore, an indication valueof the PD2DSCH may have a one-bit value. When the transmissionsynchronization source is an eNodeB, it may be recognized that theoriginal synchronization source is the eNodeB, through a root indexvalue of the PD2DSS, and thus, this may not need to be indicatedseparately.

In addition, when the transmission synchronization source is a UE andthe original synchronization source is an eNodeB, a stratum level may beindicated by a location where a D2DSS is transmitted in afrequency-resource domain or a PD2DSCH. For example, Cases 2 and 3corresponding to the condition from Table 15 may be indicated based onthe classification into two cases, that is, Case 2 in which a stratumlevel is a second stratum and Case 3 in which a stratum level is a thirdstratum. Therefore, an indication value of the PD2DSCH may have a 1-bitvalue. The stratum level when the transmission synchronization source isan eNodeB is as many as 1 event and thus, this may be recognized throughinformation associated with a type of a transmission synchronizationsource.

Also, the case in which the transmission synchronization source is anISS corresponds to Case 4, which is as many as 1 event, and this may berecognized through information associated with an originalsynchronization source, and thus, may not need to be indicatedseparately.

When the type of the synchronization source is an eNodeB, a physicallayer cell ID (N_(ID) ^(cell)) corresponding to a PCID of the eNodeB maybe used as a Physical Synchronization Source Identity (PSSID). Thephysical layer cell ID may be expressed as N_(ID) ^(cell)=3N_(ID)⁽¹⁾+N_(ID) ⁽²⁾, and N_(ID) ⁽²⁾ may be mapped in one-to-onecorrespondence to root indices of the PD2DSS that may have three values,and may have an integer in a range from 0 to 2. In this instance, theroot index of the PD2DSS may have one of 25, 29, and 34, which areidentical to the root indices of the PSS. N_(ID) ⁽¹⁾ may be mapped inone-to-one correspondence to root indices of an SD2DSS that may have 168values, and may have an integer in a range from 0 to 167. In thisinstance, a value that is identical to the SSS may be used as the valueof the SD2DSS.

Even when the type of the synchronization source is a synchronizationsource derived from an eNodeB, a Physical Synchronization SourceIdentity (PSSID) may have a value identical to the PCID of the eNodeB,and 504 unique PSSIDs may exist. The PSSID may be expressed as N_(ID)^(D2D)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾, and N_(ID) ⁽²⁾ may be mapped inone-to-one correspondence to root indices of the PD2DSS that may havethree values, and may have an integer in a range from 0 to 2. In thisinstance, newly defined root indices which are different from the rootindices of the PSS may be used as a root index of the PD2DSS, and forexample, the root indices of Table 4 may be used. For N_(ID) ⁽¹⁾, avalue of an SD2DSS that is mapped in one-to-one correspondence to an SSShaving 168 sequences may be used. Therefore, the SD2DSS may have aninteger in a range from 0 to 167, and a PSSID may be mapped to504(=3*168) IDs.

When the type of the synchronization source is an ISS or asynchronization source derived from an ISS, a Proximity based Services(ProSe) UE ID of a UE corresponding to the ISS may be used as a PhysicalSynchronization Source Identity (PSSID), and the PSSID may be mapped to504 IDs based on a predetermined mapping rule. The PSSID may beexpressed as N_(ID) ^(D2D)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾, and N_(ID) ⁽²⁾ may bemapped in one-to-one correspondence to root indices of the PD2DSS thatmay have three values, and may have an integer in a range from 0 to 2.For example, the root indices of Table 4 may be used. For N_(ID) ⁽¹⁾, avalue of an SD2DSS that is mapped in one-to-one correspondence to an SSShaving 168 sequences may be used. N_(ID) ⁽¹⁾ associated with the SD2DSSmay be mapped in one-to-one correspondence to an SSS having 168sequences and may have an integer in a range from 0 to 167. Therefore,the PSSID may be mapped to 504(=3*168) IDs.

[Embodiment 3-2]

TABLE 16 Type of SS Stratum level Case Tx SS Original SS PSSID (hopcount) Case 1: eNodeB→UE₁ eNodeB PCID of 1^(st) eNodeB eNodeB eNodeB(Index 0 (or 1)) Case 2: eNodeB→UE₁→UE₂ SS relaying eNodeB PCID of2^(nd) UE (=UE₁) eNodeB eNodeB (Index 1 (or 2)) Case 3: SS relayingeNodeB PCID of 3^(rd) eNodeB→UE₁→UE₂→UE₃ UE (=UE₂) eNodeB eNodeB (Index2 (or 3)) Case 4: ISS (=UE_(A))→ . . . →UE_(B) ISS or SS relaying ISSBased on 1^(st) UE (e.g. UE_(A)) ISS (=UE_(A)) ISS (=UE_(A)) ID (Index 0(or 1))(or not defined)

In the present embodiment, when a type of a Synchronization Source (SS)is an eNodeB, a PCID of the eNodeB may be used as a PSSID, and 504unique PSSIDs may be used. When the type of the synchronization sourceis a Synchronization Source (SS) derived from an eNodeB (SS relaying aneNodeB), a value modified based on the PCID of the eNodeB may be used asa PSSID, and 168 or K unique PSSIDs may exist, wherein K is a value thatis less than 168.

When the type of the Synchronization Source (SS) is an ISS or an SSderived from an ISS (an SS relaying an ISS), a PSSID may be determinedbased on a UE ID of the ISS, and 168 or K unique PSSIDs may exist,wherein K is a value that is less than 168.

In the present embodiment, a transmission synchronization source isindicated by a root index value of a PD2DSS. In Case 1 of Table 16, atransmission synchronization source is an eNodeB, and thus, one of 25,29, and 34, which are identical to the root indices of a PSS may be usedas a root index of a PD2DSS. Conversely, in Cases 2 to 4, newly definedroot indices, which are different from the PSS, may be used as a PD2DSS.For example, the root indices of Table 4 may be used.

Cases 2 to 4 in which a transmission synchronization source is a UE maybe classified into a case corresponding to Cases 2 and 3 in which anoriginal synchronization source is an eNodeB and a case corresponding toCase 4 in which an original synchronization source is an ISS. Forexample, when three root indices selected from Table 4 are X, Y, and Z,respectively, a transmission synchronization source may be indicated bya root index X or Y in Case 2 or 3 in which the original synchronizationsource is an eNodeB, and a transmission synchronization source may beindicated by a root index Z in Case 4 in which the originalsynchronization source is an ISS.

A stratum level may be indicated by a root index of a PD2DSS. In Case 1in which the transmission synchronization source and the originalsynchronization source are an eNodeB, the root index of the PD2DSS maybe indicated by one of 25, 29, and 34.

Cases 2 to 4 in which the transmission synchronization source is a UEmay be indicated by a newly defined root index value of the PD2DSS. Whenthree newly defined root index values of the PD2DSS are X, Y, and Z,respectively, each of Cases 2 to 4 may be indicated by X, Y, and Z. Forexample, Case 2 may b indicated by X, Case 3 may be indicated by Y, andCase 4 may be indicated by Z.

When the type of the synchronization source is an eNodeB (Case 1), aphysical layer cell ID (N_(ID) ^(cell)) corresponding to a PCID of theeNodeB may be used as a Physical Synchronization Source Identity(PSSID). The physical layer cell ID may be expressed as N_(ID)^(cell)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾, and N_(ID) ⁽²⁾ may be mapped inone-to-one correspondence to root indices of the PD2DSS that may havethree values, and may have an integer in a range from 0 to 2. In thisinstance, the root index of the PD2DSS may have one of 25, 29, and 34,which are identical to the root indices of the PSS. N_(ID) ⁽¹⁾ may bemapped in one-to-one correspondence to root indices of an SD2DSS thatmay have 168 values, and may have an integer in a range from 0 to 167.In this instance, a value that is identical to the SSS may be used asthe value of the SD2DSS.

When the type of the synchronization source is a synchronization sourcederived from an eNodeB (an SS relaying an eNodeB) (Cases 2 and 3), aPhysical Synchronization Source Identity (PSSID) may be mapped to 168 orK IDs based on a PCID of the eNodeB using a predetermined rule, whereinK is a value that is less than 168. Therefore, the PSSID may have avalue in a range from 0 to 167 or in a range from 0 to K-1. The PSSIDmay be expressed as N_(ID) ^(D2D)=N_(ID) ⁽¹⁾, and N_(ID) ⁽¹⁾ associatedwith the SD2DSS may be mapped in one-to-one correspondence to an SSSthat may have 168 values, and may have an integer in a range from 0 to167, or may be mapped in one-to-one correspondence to K values, based onsequences that are modified or partially selected from an SSS having 168sequences and may have an integer in a range from 0 to K-1, wherein K isa value less than 168. In this instance, an accurate PCID of the eNodeBmay be transmitted through a PD2DSCH.

When the type of the synchronization source is an ISS or asynchronization source derived from an ISS (Case 4), a Proximity basedServices (ProSe) UE ID of a UE corresponding to the ISS may be used as aPhysical Synchronization Source Identity (PSSID), and the PSSID may bemapped to 168 or K IDs based on a predetermined mapping rule, wherein Kis a value that is less than 168. Therefore, the PSSID may have a valuein a range from 0 to 167 or in a range from 0 to K-1. The PSSID may beexpressed as N_(ID) ^(D2D)=N_(ID) ⁽¹⁾, and N_(ID) ⁽¹⁾ associated withthe SD2DSS may be mapped in one-to-one correspondence to an SSS that mayhave 168 values, and may have an integer in a range from 0 to 167, ormay be mapped in one-to-one correspondence to K values, based onsequences that are modified or partially selected from an SSS having 168sequences and may have an integer in a range from 0 to K-1, wherein K isa value less than 168. Therefore, the PSSID may have a value in a rangefrom 0 to 167 or in a range from 0 to K-1. In this instance, an accuratePCID of the ISS may be transmitted through a PD2DSCH.

[Embodiment 3-3]

TABLE 17 Type of SS Stratum level Case Tx SS Original SS PSSID (hopcount) Case 1: eNodeB→UE₁ eNodeB PCID of 1^(st) eNodeB eNodeB eNodeB(Index 0 (or 1)) Case 2: eNodeB→UE₁→UE₂ SS relaying eNodeB PCID of2^(nd) UE (=UE₁) eNodeB eNodeB (Index 1 (or 2)) Case 3: SS relayingeNodeB PCID of 3^(rd) eNodeB→UE₁→UE₂→UE₃ UE (=UE₂) eNodeB eNodeB (Index2 (or 3)) Case 4: ISS (=UE_(A))→ . . . → UE_(B) ISS or SS relaying ISSBased on 1^(st) UE (e.g. UE_(A)) ISS (=UE_(A)) ISS (=UE_(A)) ID (Index 0(or 1))(or not defined)

In the present embodiment, when a type of a Synchronization Source (SS)is an eNodeB or an SS derived from an eNodeB (SS relaying eNodeB), aPCID of the eNodeB may be used as a Physical Synchronization SourceIdentity (PSSID), and 504 unique PSSIDs may exist.

When the type of the Synchronization Source (SS) is an ISS or an SSderived from an ISS (an SS relaying an ISS), a PSSID based on a UE ID ofthe ISS may be used, and 168 or K unique PSSIDs may exist, wherein K isa value that is less than 168.

In the present embodiment, a type of a transmission synchronizationsource may be indicated by a root index value of a PD2DSS. For example,the cases of Table 17 may be classified into two cases, that is, a casecorresponding to Case 1 in which a transmission synchronization sourceis an eNodeB and the other case corresponding to Cases 2 to 4 in which atransmission synchronization source is a UE, and each case may beindicated by a root index value of a PD2DSS. A PD2DSS when thetransmission synchronization source is an eNodeB, may use 25, 29, and34, which are identical to the root indices of a PSS A PD2DSS when thetransmission synchronization source is a UE, may use newly defined rootindices which are different from the root indices of a PSS. For example,the root indices of Table 4 may be used.

When the transmission synchronization source is a UE, a type of anoriginal synchronization source may be indicated by a Physical D2DSynchronization Channel (PD2DSCH). For example, Cases 2 to 4 of Table 17may be indicated based on the classification into two cases, that is, acase corresponding to Cases 2 and 3 in which a type of an originalsynchronization source is an eNodeB and the other case corresponding toCase 4 in which a type of an original synchronization source is anIndependent Synchronization Source (ISS). Therefore, an indication valueof the PD2DSCH may have a one-bit value.

When the transmission synchronization source is a UE and the originalsynchronization source is an eNodeB, a stratum level may be indicated bya location where a D2DSS is transmitted in a frequency-resource domainor a PD2DSCH. For example, Cases 2 and 3 corresponding to the conditionfrom Table 15 may be indicated based on the classification into twocases, that is, Case 2 in which a stratum level is a second stratum andCase 3 in which a stratum level is a third stratum. Therefore, anindication value of the PD2DSCH may have a 1-bit value.

The stratum level when the transmission synchronization source is aneNodeB is as many as 1 event and thus, it may be recognized throughinformation associated with a type of a transmission synchronizationsource. Also, the case in which the transmission synchronization sourceis an ISS corresponds to Case 4, which is as many as 1 event, and thus,it may be recognized through information associated with an originalsynchronization source, and thus, this may not need to be indicatedseparately.

When the type of the synchronization source is an eNodeB, a physicallayer cell ID (N_(ID) ^(cell)) corresponding to a PCID of the eNodeB maybe used as a Physical Synchronization Source Identity (PSSID). Thephysical layer cell ID may be expressed as N_(ID) ^(cell)=3N_(ID)⁽¹⁾+N_(ID) ⁽²⁾, and N_(ID) ⁽²⁾ may be mapped in one-to-onecorrespondence to root indices of the PD2DSS that have three values, andmay have an integer in a range from 0 to 2. In this instance, the rootindex of the PD2DSS may have one of 25, 29, and 34, which are identicalto the root indices of the PSS. N_(ID) ⁽¹⁾ may be mapped in one-to-onecorrespondence to root indices of an SD2DSS that may have 168 values,and may have an integer in a range from 0 to 167. In this instance, avalue that is identical to the SSS may be used as the value of theSD2DSS.

Even when the type of the synchronization source is a synchronizationsource derived from an eNodeB, a Physical Synchronization SourceIdentity (PSSID) may have a value identical to the PCID of the eNodeB,and 504 unique PSSIDs may exist. The PSSID may be expressed as N_(ID)^(D2D)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾, and N_(ID) ⁽²⁾ may be mapped inone-to-one correspondence to root indices of the PD2DSS that may havethree values, and may have an integer in a range from 0 to 2. In thisinstance, newly defined root indices which are different from the rootindices of the PSS may be used as a root index of the PD2DSS, and forexample, the root indices of Table 4 may be used. For N_(ID) ⁽¹⁾, avalue of an SD2DSS that is mapped in one-to-one correspondence to an SSShaving 168 sequences may be used. Therefore, the SD2DSS may have aninteger in a range from 0 to 167, and a PSSID may be mapped to504(=3*168) IDs.

When the type of the synchronization source is an ISS or asynchronization source derived from an ISS (Case 4), a Proximity basedServices (ProSe) UE ID of a UE corresponding to the ISS may be used as aPhysical Synchronization Source Identity (PSSID), and the PSSID may bemapped to 168 or K IDs based on a predetermined mapping rule, wherein Kis a value that is less than 168. Therefore, the PSSID may have a valuein a range from 0 to 167 or in a range from 0 to K-1. The PSSID may beexpressed as N_(ID) ^(D2D)=N_(ID) ⁽¹⁾, and N_(ID) ⁽¹⁾ associated withthe SD2DSS may be mapped in one-to-one correspondence to an SSS that mayhave 168 values, and may have an integer in a range from 0 to 167, ormay be mapped in one-to-one correspondence to K values, based onsequences that are modified or partially selected from an SSS having 168sequences and may have an integer in a range from 0 to K-1, wherein K isa value less than 168. Therefore, the PSSID may have a value in a rangefrom 0 to 167 or in a range from 0 to K-1. In this instance, an accurateUE ID of the ISS may be transmitted through a PD2DSCH.

[Embodiment 3-4]

TABLE 18 Type of SS Stratum level Case Tx SS Original SS PSSID (hopcount) Case 1: eNodeB→UE₁ eNodeB PCID of 1^(st) eNodeB eNodeB eNodeB(Index 0 (or 1)) Case 2: eNodeB→UE₁→UE₂ SS relaying eNodeB Based on2^(nd) UE (=UE₁) eNodeB UE (=UE₁) ID (Index 1 (or 2)) Case 3: SSrelaying eNodeB Based on 3^(rd) eNodeB→UE₁→UE₂→UE₃ UE (=UE₂) eNodeB UE(=UE₂) ID (Index 2 (or 3)) Case 4: ISS (=UE_(A))→ . . . → UE_(B) ISS orSS relaying ISS Based on 1^(st) UE (e.g. UE_(A)) ISS (=UE_(A)) UE (e.g.UE_(A)) (Index 0 (or ID 1))(or not defined)

In the present embodiment, when the type of the Synchronization Source(SS) is an eNodeB, a PCID of the eNodeB may be used as a PhysicalSynchronization Source Identity (PSSID), and 504 unique PSSIDs mayexist.

When the type of the Synchronization Source (SS) is an SS derived froman eNodeB (an SS relaying an eNodeB), an ISS, or an SS derived from anISS (an SS relaying an ISS), a PSSID based on a UE ID of a transmissionsynchronization source may be used as a PSSID, and 504 unique PSSIDs mayexist.

In the present embodiment, a type of a transmission synchronizationsource may be indicated by a root index value of a PD2DSS. For example,the cases of Table 18 may be classified into two cases, that is, a casecorresponding to Case 1 in which a transmission synchronization sourceis an eNodeB and the other case corresponding to Cases 2 to 4 in which atransmission synchronization source is a UE, and each case may beindicated by a root index value of a PD2DSS. A PD2DSS when thetransmission synchronization source is an eNodeB, may use 25, 29, and34, which are identical to the root indices of a PSS A PD2DSS when thetransmission synchronization source is a UE may use newly defined rootindices which are different from the root indices of a PSS. For example,the root indices of Table 4 may be used.

When the transmission synchronization source is a UE, a type of anoriginal synchronization source may be indicated by a Physical D2DSynchronization Channel (PD2DSCH). For example, the cases of Table 18may be indicated based on the classification into two cases, that is, acase corresponding to Cases 2 and 3 in which a type of an originalsynchronization source is an eNodeB and the other case corresponding toCase 4 in which a type of an original synchronization source is anIndependent Synchronization Source (ISS). Therefore, an indication valueof the PD2DSCH may have a one-bit value.

A stratum level when the synchronization source is an eNodeB does notexist, excluding Case 1, and thus, this may be recognized throughinformation associated with a transmission synchronization source.Therefore, this may not need to be separately indicated.

When the synchronization source is an SS derived from an eNodeB (an SSrelaying an eNodeB), a stratum level may be indicated by a locationwhere a D2DSS is transmitted in a frequency-resource domain or aPD2DSCH. For example, cases of Table 18 may be classified into twocases, that is, a case corresponding to Case 2 in which a stratum levelis 2 and a case corresponding to Case 3 in which a stratum level is 3.Therefore, an indication value of the PD2DSCH may have a 1-bit value.

When a type of the synchronization source is an eNodeB, a physical layercell ID (N_(ID) ^(cell)) corresponding to a PCID of the eNodeB may beused as a Physical Synchronization Source Identity (PSSID). The physicallayer cell ID may be expressed as N_(ID) ^(cell)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾,and N_(ID) ⁽²⁾ may be mapped in one-to-one correspondence to rootindices of the PD2DSS that may have three values, and may have aninteger in a range from 0 to 2. In this instance, the root index of thePD2DSS may have one of 25, 29, and 34, which are identical to the rootindices of the PSS. N_(ID) ⁽¹⁾ may be mapped in one-to-onecorrespondence to root indices of an SD2DSS that may have 168 values,and may have an integer in a range from 0 to 167. In this instance, avalue that is identical to the SSS may be used as the value of theSD2DSS.

When the type of the synchronization source is a synchronization sourcederived from an eNodeB (an SS relaying an eNodeB), an ISS, or asynchronization source derived from an ISS (an SS relaying an ISS), aProximity based Services (ProSe) UE ID of a transmission (Tx) UE may beused as a Physical Synchronization Source Identity (PSSID), and thePSSID may be mapped to 504 IDs based on a predetermined mapping rule.The PSSID may be expressed as N_(ID) ^(D2D)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾, andN_(ID) ⁽²⁾ may be mapped in one-to-one correspondence to root indices ofthe PD2DSS that may have three values, and may have an integer in arange from 0 to 2. In this instance, newly defined root indices whichare different from the root indices of the PSS may be used as a rootindex of the PD2DSS, and for example, the root indices of Table 4 may beused. N_(ID) ⁽¹⁾ associated with the SD2DSS may be mapped in one-to-onecorrespondence to an SSS having 168 sequences and may have an integer ina range from 0 to 167. Therefore, the PSSID may be mapped to 504(=3*168)IDs.

[Embodiment 3-5]

TABLE 19 Type of SS Stratum level Case Tx SS Original SS PSSID (hopcount) Case 1: eNodeB→UE₁ eNodeB PCID of 1^(st) eNodeB eNodeB eNodeB(Index 0 (or 1)) Case 2: eNodeB→UE₁→UE₂ SS relaying eNodeB Based on2^(nd) UE (=UE₁) eNodeB UE (=UE₁) ID (Index 1 (or 2)) Case 3: SSrelaying eNodeB Based on 3^(rd) eNodeB→UE₁→UE₂→UE₃ UE (=UE₂) eNodeB UE(=UE₂) ID (Index 2 (or 3)) Case 4: ISS (=UE_(A))→ . . . → UE_(B) ISS orSS relaying ISS Based on 1^(st) UE (e.g. UE_(A)) ISS (=UE_(A)) UE (e.g.UE_(A)) (Index 0 (or ID 1))(or not defined)

In the present embodiment, when a type of a Synchronization Source (SS)is an eNodeB, a PCID of the eNodeB may be used as a PhysicalSynchronization Source Identity (PSSID), and 504 unique PSSIDs mayexist.

When the type of the Synchronization Source (SS) is an SS derived froman eNodeB (an SS relaying an eNodeB), an ISS, or an SS derived from anISS (an SS relaying an ISS), a PSSID based on a UE ID of a transmissionsynchronization source may be used, and 168 or K unique PSSIDs mayexist, wherein K is a value less than 168.

In the present embodiment, a type of a transmission synchronizationsource may be indicated by a root index value of a PD2DSS. For example,cases of Table 19 may be classified into two cases, that is, a casecorresponding to Case 1 in which a transmission synchronization sourceis an eNodeB and the other case corresponding to Cases 2 to 4 in which atransmission synchronization source is a UE, and each case may beindicated by a root index value of a PD2DSS. A PD2DSS when thetransmission synchronization source is an eNodeB, may use 25, 29, and34, which are identical to the root indices of a PSS. A PD2DSS when thetransmission synchronization source is a UE, may use newly defined rootindices which are different from the root indices of a PSS. For example,the root indices of Table 4 may be used.

Cases 2 to 4 in which a transmission synchronization source is a UE maybe classified into a case corresponding to Cases 2 and 3 in which anoriginal synchronization source is an eNodeB and a case corresponding toCase 4 in which an original synchronization source is an ISS. Forexample, when three root indices selected from Table 4 are X, Y, and Z,respectively, a transmission synchronization source may be indicated bya root index X or Y in Case 2 or 3 in which the original synchronizationsource is an eNodeB, and a transmission synchronization source may beindicated by a root index Z in Case 4 in which the originalsynchronization source is an ISS.

A stratum level may be indicated by a root index of a PD2DSS. In Case 1in which the transmission synchronization source and the originalsynchronization source are an eNodeB, the root index of the PD2DSS maybe indicated by one of 25, 29, and 34.

Cases 2 to 4 in which the transmission synchronization source is a UEmay be indicated by a newly defined root index value of the PD2DSS. Whenthree newly defined root index values of the PD2DSS are X, Y, and Z,respectively, each of Cases 2 to 4 may be indicated by X, Y, and Z. Forexample, Case 2 may be indicated by X, Case 3 may be indicated by Y, andCase 4 may be indicated by Z.

When the type of the synchronization source is an eNodeB, a physicallayer cell ID (N_(ID) ^(cell)) corresponding to a PCID of the eNodeB maybe used as a Physical Synchronization Source Identity (PSSID). Thephysical layer cell ID may be expressed as N_(ID) ^(cell)=3N_(ID)⁽¹⁾+N_(ID) ⁽²⁾, and N_(ID) ⁽²⁾ may be mapped in one-to-onecorrespondence to root indices of the PD2DSS that may have three values,and may have an integer in a range from 0 to 2. In this instance, theroot index of the PD2DSS may have one of 25, 29, and 34, which areidentical to the root indices of the PSS. N_(ID) ⁽¹⁾ may be mapped inone-to-one correspondence to root indices of an SD2DSS that may have 168values, and may have an integer in a range from 0 to 167. In thisinstance, a value that is identical to the SSS may be used as the valueof the SD2DSS.

When the type of the synchronization source is a synchronization sourcederived from an eNodeB (an SS relaying an eNodeB), an ISS, or asynchronization source derived from an ISS (an SS relaying an ISS), aPhysical Synchronization Source Identity (PSSID) is based on a Proximitybased Services (ProSe) UE of a transmission (Tx) UE, and may be mappedto 168 or K IDs based on a predetermined mapping rule, wherein K is avalue less than 168. Therefore, the PSSID may have a value in a rangefrom 0 to 167 or in a range from 0 to K-1. The PSSID may be expressed byN_(ID) ^(D2D)=N_(ID) ⁽¹⁾, and N_(ID) ⁽¹⁾ associated with an SD2DSS maybe mapped in one-to-one correspondences to an SSS having 168 sequences,or may be mapped to K sequences based on sequences modified or partiallyselected from the SSS having 168 sequences, wherein K is a value lessthan 168. When N_(ID) ⁽¹⁾ is mapped in one-to-one correspondence to 168sequences, it may have an integer in a range from 0 to 167, and when itis mapped in one-to-one correspondence to K sequences, it may have aninteger in a range from 0 to K-1. In this instance, an accurate UE ID ofthe transmission synchronization source may be transmitted through aPD2DSCH.

FIG. 5 is a block diagram of a wireless communication system accordingto one or more exemplary embodiments.

Referring to FIG. 5, a D2D synchronization source 500 includes a RadioFrequency (RF) unit 505, a processor 510, and a memory 515. The memory515 is connected to the processor 510, and stores various pieces ofinformation for driving the processor 510. The RF unit 505 is connectedto the processor 510, and transmits and/or receives a wireless signal.For example, the RF unit 505 may transmit a D2DSS to a D2D receiving UE550.

The processor 510 may implement proposed functions, processes, and/ormethods. In particular, the processor 510 may execute all operationsassociated with FIGS. 2 to 4. For example, the processor 510 may includea synchronization information determining unit 511 and a D2DSSgenerating unit 513.

The synchronization information determining unit 511 may determinesynchronization information for generating a D2DSS. The synchronizationinformation may include a type of a synchronization source, a PhysicalSynchronization Source Identity (PSSID), and a stratum level.

The D2DSS generating unit 513 generates a D2DSS based on the type ofsynchronization source, the PSSID, the stratum level information,determined in the synchronization information determining unit 511. TheD2DSS may include a PD2DSS, an SD2DSS, and a PD2DSCH. The type ofsynchronization source, the Physical Synchronization Source Identity(PSSID), and stratum level information may be indicated by the D2DSS,and some of the information may be indicated by a location of the D2DSSin a subframe.

According to one or more exemplary embodiments, information associatedwith a synchronization source, such as a type of a SynchronizationSource (SS), a Physical Synchronization Source Identity (PSSID), astratum level, and the like, may be estimated based on a received D2DSS.Operations of the UE 500 may be implemented by the processor 510.

The memory 515 is connected to the processor 510, and stores variouspieces of information for driving the processor 510. For example, thememory 515 may store synchronization information, and may store aPD2DSS, an SD2DSS, a PD2DSCH, and a location where a D2DSS is receivedin time-frequency resource domain. Also, in response to a request fromthe processor 510, the memory 515 may provide the synchronizationinformation to the processor 510.

The D2D receiving UE 550 may include a processor 555, a memory 560, anda Radio Frequency (RF) unit 565. The RF unit 565 is connected to theprocessor 555, and transmits and/or receives a wireless signal. Theprocessor 555 may implement proposed functions, processes, and/ormethods. For example, the processor 555 may include a D2DSS determiningunit 557, and a synchronization unit 559.

The D2D determining unit 557 may determine a D2DSS received from the D2Dsynchronization source 500, so as to estimate synchronizationinformation indicated by the received D2DSS. The synchronizationinformation may include a type of a synchronization source, a PhysicalSynchronization Source Identity (PSSID), and a stratum level. The D2DSSthat indicates the synchronization information may include a PD2DSS, anSD2DSS, and a PD2DSCH. Some of the synchronization information may beindicated by a location of a D2DSS in a subframe.

The synchronization unit 512 may obtain synchronization with asynchronization source, using information obtained through the D2DSS.

The processor 510 of the D2D synchronization source 500 or the processor555 of the D2D receiving UE 550 may include an application-specificintegrated circuit (ASIC), another chipset, a logic circuit, and/or adata processing device. The memory may include a Read-Only Memory (ROM),a Random Access Memory (RAM), a flash memory, a memory card, a storagemedium and/or another storage device. The RF unit may include a basebandcircuit for processing a wireless signal. When the embodiment isembodied as software, the described scheme may be embodied as a module(process, function, or the like) that executes the described function.The module may be stored in a memory, and may be executed by aprocessor. The memory may be disposed inside or outside the processor,and may be connected to the processor through various well-known means.

In the described exemplary system, although methods are described basedon a flowchart as a series of steps or blocks, aspects of the presentinvention are not limited to the sequence of the steps and a step may beexecuted in a different order or may be executed in parallel withanother step. In addition, it is apparent to those skilled in the artthat the steps in the flowchart are not exclusive, and another step maybe included or one or more steps of the flowchart may be omitted withoutaffecting the scope of the present invention.

Hereinafter, a method of configuring a D2DSS based on synchronizationinformation will be described in detail. First, a method of configuringa PD2DSS will be described, with respect to different types ofsynchronization sources. Although the description provided below isbased when the maximum stratum level is a third layer (a second layerwhen an eNodeB is excluded) in cases where an original synchronizationsource is an eNodeB, and when the maximum stratum level is a first layer(or not defined) in cases where an original synchronization source is anISS, as illustrated in FIG. 4, they may be applied to the case mentionedthrough FIGS. 2 and 3.

Configuration 1) when a synchronization source is an eNodeB

In this instance, a PD2DSS is a synchronization signal transmitted froman eNodeB to a UE, and the UE may be a UE in the network coverage(in-coverage UE). In this instance, both an original synchronizationsource and a transmission synchronization source are an eNodeB, andthus, a PD2DSS identical to a PSS may be transmitted. Therefore, a rootindex of the PD2DSS which is identical to the PSS may have one of 25,29, and 34.

Referring again to FIG. 4, this may correspond to a transmission fromthe eNodeB 400 to the first UE 410.

Configuration 2) when a synchronization source is an SS derived from aneNodeB (an SS relaying an eNodeB), and a transmission UE is a UE in thenetwork coverage, e.g., in the coverage of an eNodeB, (in-coverage UE)

In this instance, a transmitted PD2DSS is a synchronization signalmodified from a PSS (for example, a root index or the like), and thePD2DSS may be configured from a D2DSS sequence included in D2DSSue_net.The D2DSSue_net indicates a set of D2DSS sequences transmitted from a UEof which a transmission timing reference is an eNodeB. Transmission ofthe D2D synchronization signal is a transmission from a UE to a UE, atransmission (Tx) UE is an in-coverage UE, and a reception (Rx) UE is aUE outside the network coverage (out-coverage UE).

Here, the Tx UE receives, from an eNodeB, a synchronization signalgenerated from a PSS/SSS, and transmits, to the Rx UE, synchronizationinformation obtained through the reception through a synchronizationsignal generated from a first D2DSS sequence (a first PD2DSS sequence+afirst SD2DSS sequence) included in the D2DSSue_net.

Referring again to FIG. 4, this may correspond to a transmission fromthe first UE 410 to the second UE 420. In this instance, a newly definedroot index, which is different from a root index of a PSS, may be usedas a root index of a PD2DSS, and the root index of the PD2DSS may bedefined by Table 4. When three newly defined root indices are X, Y, andZ, respectively, X may be used for this case. That is, X may be used asa root index for the first PD2DSS sequence.

Configuration 3) when a synchronization source is an SS derived from aneNodeB (an SS relaying an eNodeB), and a transmission UE is a UE outsideof the network coverage, e.g., outside of a coverage of an eNodeB,(out-coverage UE)

In this instance, a transmitted PD2DSS may be configured from a D2DSSsequence included in the D2DSSue_net, in the same manner as the case inwhich a transmission UE is an in-coverage UE. In this instance, both aTx UE and a Rx UE may be out-coverage UEs.

Here, the Tx UE receives a synchronization signal generated from a firstD2DSS sequence (a first PD2DSS sequence+a first SD2DSS sequence)included in the D2DSSue_net, from an in-coverage UE, and transmits, tothe Rx UE, synchronization information obtained through the reception,through a synchronization signal generated from a second D2DSS sequence(a second PD2DSS sequence+a second SD2DSS sequence) included in theD2DSSue_net.

Referring again to FIG. 4, this may correspond to a transmission fromthe second UE 420 to the third UE 430. In this instance, a newly definedroot index, which is different from a root index of a PSS, may be usedas a root index of a PD2DSS, and the root index of the PD2DSS may bedefined by Table 4. When three newly defined root indices are X, Y, andZ, respectively, Y may be used, which is different from a root indexused when a transmission UE is an in-coverage UE. That is, Y may be usedas a root index for the second PD2DSS sequence.

Configuration 4) when a synchronization source is an ISS or an SSderived from an ISS (an SS relaying an ISS)

In this instance, a transmitted PD2DSS may be a synchronization signalmodified from a PSS (for example, a root index or the like). The PD2DSSmay be configured from a D2DSS sequence included in D2DSSue_oon, and maybe transmitted. The D2DSSue_oon indicates a set of D2DSS sequencestransmitted from a UE of which a transmission timing reference is not aneNodeB. In this instance, both a Tx UE and an Rx UE may be out-coverageUEs, and the Tx UE may be an ISS or an SS derived from an ISS (an SSrelaying an ISS).

Here, when the Tx UE is an ISS, the Tx UE may transmit synchronizationinformation of itself to the Rx UE through a synchronization signalgenerated from a third D2DSS sequence (a third PD2DSS sequence+a thirdSD2DSS sequence) included in the D2DSSue_oon.

Here, when the Tx UE is an SS derived from an ISS, the Tx UE receives,from the ISS or another SS derived from the ISS, a synchronizationsignal generated from the third D2DSS sequence (the third PD2DSSsequence+the third SD2DSS sequence) included in the D2DSSue_oon, and mayor may not transmit, to the reception (Rx) UE, the synchronizationinformation obtained through the reception, through the synchronizationsignal generated from the third D2DSS sequence (the third PD2DSSsequence+third SD2DSS sequence) included in the D2DSSue_oon, as occasionarises.

Referring again to FIG. 4, this may correspond to a transmission fromthe fourth UE 440 to the fifth UE 450. In this instance, a newly definedroot index, which is different from a root index of a PSS, may be usedas a root index of a PD2DSS, and the root index of the PD2DSS may bedefined by Table 4. When three newly defined root indices are X, Y, andZ, respectively, Z may be used as a root index, which is different fromX and Y which are used when a synchronization source is an SS derivedfrom an eNodeB (an SS relaying an eNodeB). That is, Z may be used as aroot index for the third PD2DSS sequence.

Hereinafter, a method of configuring a PD2DSS when a D2D reception (Rx)UE is inside or outside the network coverage, will be described.

1) D2D reception (Rx) UE inside the network coverage

A D2D Rx UE inside the network coverage detects a PSS/SSS from aneNodeB, and selects the same as a timing reference. In this instance,the PSS may correspond to the PSS of the configuration 1. The D2D Rx UEinside the network coverage may detect a D2DSS in addition to thePSS/SSS from the eNodeB, but may prioritize the PSS/SSS from the eNodeBand select the same as a timing reference. The D2D Rx UE may transmit aD2DSS to another UE. In this instance, a transmitted PD2DSS maycorrespond to the PD2DSS of the configuration 2.

2) D2D reception (Rx) UE outside the network coverage

The D2D Rx UE outside the network coverage may detect one or more D2DSSsfrom one or more UEs and may select one of the signals as a timingreference. In this instance, a D2D Tx UE may be one of an ISS, an SSderived from an eNodeB (an SS relaying an eNodeB), and an SS derivedfrom an ISS (an SS relaying an ISS). When the D2DSS is not detected, theD2D Rx UE itself may act as an ISS. In this instance, a root index ofthe detected PD2DSS may be one of X, Y, and Z. Hereinafter, a timingreference selecting method for each case and a method of transmitting aPD2DSS when a D2D Rx UE is a new synchronization source, will bedescribed.

a) when a PD2DSS of which a root index is X is received and selected asa timing reference

In this instance, a D2D Rx UE detects a D2DSS including a PD2DSScorresponding to the configuration 2, and selects the same as a timingreference. When the UE is a synchronization source of the D2DSS, the UEmay transmit a D2DSS. In this instance, a transmitted PD2DSS may beconfigured as a PD2DSS of the configuration 3.

a) when a PD2DSS of which a root index is Y is received and selected asa timing reference

In this instance, a D2D Rx UE detects a D2DSS including a PD2DSScorresponding to the configuration 3, and selects the same as a timingreference. When the UE is a synchronization source of the D2DSS, the UEmay transmit a D2DSS. In this instance, a transmitted PD2DSS may beconfigured as a PD2DSS of the configuration 3.

a) when a PD2DSS of which a root index is Z is received and selected asa timing reference

In this instance, a D2D Rx UE detects a D2DSS including a PD2DSScorresponding to the configuration 4, and selects the same as a timingreference. When the UE is a synchronization source of the D2DSS, the UEmay transmit a D2DSS. In this instance, a transmitted PD2DSS may beconfigured as a PD2DSS of the configuration 4.

d) when a D2DSS is not detected

In this instance, a D2D Rx UE may act as an ISS and transmits a D2DSS.In this instance, a transmitted PD2DSS may be configured as a PD2DSS ofthe configuration 4.

When the D2D Rx UE receives all PD2DSSs of which root indices are X, Y,and Z, a timing reference may be selected in order of X>Y>Z, or indifferent order of priority.

Hereinafter, when an original synchronization source is an eNodeB or anISS, a method of configuring PD2DSSs of the configurations 1 to 4 basedon each hop count and a stratum level will be described.

First, when an original synchronization source is an eNodeB, a stratumlevel and a configuration of a D2DSS will be described for each hopcount. When the hop count is 1, the stratum level is set to 0 and atransmitted D2DSS may include a PSS of the configuration 1. When the hopcount is 2, the stratum level is set to 1 and a transmitted D2DSS mayinclude a PD2DSS of the configuration 2. When the hop count is 3, thestratum level is set to 2 and a transmitted D2DSS may include a PD2DSSof the configuration 3. When the hop count is 4 or more, the stratumlevel is set to 2 and a transmitted D2DSS may include a PD2DSS of theconfiguration 3. The configurations may be applied to the embodimentsthat have been described with reference to FIGS. 2 to 4, and otherconfigurations may be applied to other embodiments.

Subsequently, when an original synchronization source is an ISS, astratum level and a configuration of a D2DSS will be described for eachhop count. When the hop count is 1, the stratum level is set to 0 and atransmitted D2DSS may include a PD2DSS of the configuration 4. When thehop count is 1 or more, the stratum level is set to 0 and a transmittedD2DSS may include a PD2DSS of the configuration 4. The configurationsmay be applied to the embodiments that have been described withreference to FIG. 4, and other configurations may be applied to otherembodiments.

A sequence of an SD2DSS may be defined to use one of 168 sequences thatare generated by interleaving two binary sequences having a length of31, in the same manner as a sequence of an SSS, or may be defined to useonly K sequences based on sequences modified or partially selected fromthe SSS having 168 sequences. In this instance, K may be an integer lessthan 168.

FIG. 6 is a flowchart illustrating an example of a method in which a D2DRx UE selects a D2D transmission mode based on a root index value of areceived PD2DSS according to one or more exemplary embodiments.

Referring to FIG. 6, a method of estimating a D2D transmission modeincludes: receiving at least one D2DSS in operation S605, and extractinga PD2DSS from the received D2DSS so as to estimate a root index of thePD2DSS in operation S615. Subsequently, the D2D Rx UE determines whethera D2DSS of which a root index value corresponds to one of 25, 29 and 34exists in operation S620, and, when it is determined that thecorresponding D2DSS exists, the D2D transmission mode select the D2DSSof the configuration 1 as a timing reference S625.

When it is determined that a corresponding root index value does notexist in operation S620, the D2D Rx UE determines whether a root indexvalue of a PD2DSS corresponding to X exists among previously definedvalues in operation S630, and when it is determined that a correspondingroot index value exists, the D2D Rx UE selects a D2DSS of theconfiguration 2 as a timing reference in operation 635. The previouslydefined root index values may be one of the root indices of Table 4, ora first value of the three root indices may be set to X.

When it is determined that a corresponding root index value does notexist in operations S620 and S630, the D2D Rx UE determines whether aroot index value of a PD2DSS corresponding to Y exists among previouslydefined values in operation S640, and when it is determined that acorresponding root index value exists, the D2D Rx UE selects a D2DSS ofthe configuration 3 as a timing reference in operation 645. Thepreviously defined root index values may be one of the root indices ofTable 4, or a second value of the three root indices may be set to Y.

When it is determined that a corresponding root index value does notexist in operations S620, S630, and S640, the D2D Rx UE determineswhether a root index value of a PD2DSS corresponding to Z exists amongpreviously defined values in operation S650, and when it is determinedthat a corresponding root index value exists, the D2D Rx UE selects aD2DSS of the configuration 4 as a timing reference in operation 655. Thepreviously defined root index values may be one of the root indices ofTable 4, or a third value of the three root indices may be set to Z.

When root indices corresponding to 25, 29, 34, X, Y, and Z are notdetected in operations S620, 630, 640, and 650, the UE itself act as anISS and transmits a D2DSS in operation S660. In this instance, thetransmitted D2DSS may be configured to include a PD2DSS of theconfiguration 4.

Exemplary embodiments provide a root index of a PD2DSS used for eachconfiguration type. In the case of the configuration 1 (a PSS/SSSconfiguration when a synchronization source is an eNodeB), one of 25,29, and 34 which are root indices of a PSS is used as a root index of aPD2DSS. In the case of the configuration 2 (a D2DSS sequenceconfiguration included in D2DSSue_net when a synchronization source isan SS derived from an eNodeB (an SS relaying an eNodeB) and a Tx UE isan in-coverage UE), one of three new root indices is used (for example,X which is a first value of the three new root indices of Table 4). Inthe case of the configuration 3 (a D2DSS sequence configuration includedin D2DSSue_net when a synchronization source is an SS derived from aneNodeB (an SS relaying an eNodeB), and a Tx UE is an out-coverage UE),another of the three new root indices is used (for example, Y which is asecond value of the three new root indices of Table 4). In the case ofthe configuration 4 (a D2DSS sequence configuration included inD2DSSue_oon when a synchronization source is an ISS or an SS derivedfrom an ISS (an SS relaying an ISS)), the other of the three new rootindices is used (for example, Z which is a third value of the three newroot indices of Table 4).

When the three new root indices are not defined and only the threeexisting root indices, 25, 29, and 34, are used, one of 25, 29, and 34may be configured as X (for example, X=25), another as Y (for example,Y=29), and the other as Z (for example, Z=34).

As noted above, a type of an original synchronization source, e.g., aneNodeB or an Independent Synchronization Source (ISS) may be indicatedby information other than a root index, e.g., an indication value of thePD2DSCH that may have a one-bit value. Further, it may be determinedwhether a transmission synchronization source is an in-coverage UE or anout-of-coverage UE based on information other than a root index.

Further, according to one or more exemplary embodiments, a UE supportinga D2D communication may receive a synchronization signal transmittedfrom a synchronization source, determine a root index based on thereceived synchronization signal, determine a synchronization timingreference based on the root index, and transmit a synchronization signalfor a D2D communication based on the determined synchronization timingreference. The UE may receive more than one synchronization signalstransmitted from different synchronization sources, respectively. If thereceived synchronization signals meet certain requirements, e.g.,received signal power, the UE may choose one of the receivedsynchronization signals and select one corresponding referencesynchronization source for synchronization of the UE. By selecting onesynchronization source, the UE may determine the synchronization timingreference based on the corresponding synchronization signal. Asynchronization signal transmitted from a synchronization source mayinclude a primary synchronization signal and a secondary synchronizationsignal. The secondary synchronization signal may be transmitted togetherwith the primary synchronization signal or transmitted separately fromthe primary synchronization signal.

The UE may determine a category of a synchronization source based on aroot index relating to a primary synchronization signal transmitted fromthe synchronization source. The primary synchronization signal may bedetermined as a PSS transmitted by an eNodeB or a PD2DSS transmitted bya UE based on a root index associated with the received primarysynchronization signal.

Then, the UE may prioritize the synchronization source based ondetermining whether the synchronization source is an eNodeB, a UEsynchronized with an eNodeB, or a UE having a synchronization timingreference independent from an eNodeB. The synchronization timingreference and/or the reference synchronization source may be determinedbased on the prioritization.

The UE may further determine whether the synchronization source is a UElocated in a coverage of an eNodeB or a UE located out of a coverage ofan eNodeB, among UEs synchronized with an eNodeB. In this configuration,the UE may prioritize the synchronization source further based ondetermining whether the synchronization source is a UE located in acoverage of an eNodeB or a UE located out of a coverage of an eNodeB.Here, the UE synchronized with an eNodeB may be a UE directlysynchronized with an eNodeB or a UE having an eNodeB as an originalsynchronization source.

Once the UE selects the reference synchronization source from which theUE completes its own synchronization process, the UE may generate asynchronization signal for a D2D communication with a target UE based onthe category of the reference synchronization source. For example, theUE may generate the synchronization signal for a D2D communication withthe target UE based on a set for in-coverage (D2DSSue_net) when aneNodeB or a UE synchronized with an eNodeB is selected as the referencesynchronization source. Further, the UE may generate the synchronizationsignal for a D2D communication with the target UE based on a set forout-of-coverage (D2DSSue_oon) when a UE having a synchronization timingreference independent from an eNodeB is selected as the referencesynchronization source. Since the UE is not an eNodeB, thesynchronization signal for a D2D communication with the target UE isrelated to a root index different from the root indexes 25, 29, and 34.

According to one or more exemplary embodiments, the synchronizationsignal for a D2D communication with the target UE may include a primaryD2D synchronization signal associated with a root index corresponding toa number different from 25, 29, and 34 and a secondary D2Dsynchronization signal. The primary D2D synchronization signal and thesecondary D2D synchronization signal may be transmitted throughdifferent frequency-time resources. The secondary D2D synchronizationsignal may be generated based on one of 168 identities corresponding tothe set for in-coverage (D2DSSue_net) or one of 168 identitiescorresponding to the set for out-of-coverage (D2DSSue_oon).

Without selecting a synchronization reference source, the UE mayindependently determine a synchronization timing reference, therebybecoming an independent synchronization source not associated with asynchronization timing of an eNodeB. The UE may transmit asynchronization signal determined based on a set for out-of-coverage(D2DSSue_oon), when the UE serves as an independent synchronizationsource (ISS) or the UE selects a reference synchronization timing sourceoriginated from a UE serving as an ISS.

According to one or more exemplary embodiments, D2D synchronizationinformation may be efficiently indicated based on an apparatus thattransmits or receives a D2D signal.

The above description is to explain exemplary embodiments of inventiveconcept, and it will be apparent to those skills in the art thatmodifications and variations can be made without departing from thespirit and scope of inventive concept. Thus, it is intended that thepresent invention cover the modifications and variations of exemplaryembodiments provided they come within the scope of the appended claimsand their equivalents.

What is claimed is:
 1. A first wireless communication device comprising:a receiver to receive a synchronization signal transmitted from asynchronization source; a processor to determine a root index based onthe received synchronization signal, and to determine a synchronizationtiming reference based on the root index; and a transmitter to transmit,based on the determined synchronization timing reference, asynchronization signal for a direct communication between the firstwireless communication device and a second wireless communicationdevice, wherein determining, by the processor, the synchronizationtiming reference comprises: based on the root index, determining acategory of the synchronization source; prioritizing the synchronizationsource based on determining whether the synchronization source is anevolved NodeB (eNodeB), a wireless communication device synchronizedwith an eNodeB, or a wireless communication device having asynchronization timing reference independent from an eNodeB; determiningwhether the synchronization source is a wireless communication devicelocated in a coverage of an eNodeB or a wireless communication devicelocated out of a coverage of an eNodeB, among wireless communicationdevices synchronized with an eNodeB; prioritizing the synchronizationsource further based on determining whether the synchronization sourceis a wireless communication device located in a coverage of an eNodeB ora wireless communication device located out of a coverage of an eNodeB;and determining the synchronization timing reference based on theprioritization.
 2. The first wireless communication device of claim 1,wherein determining, by the processor, the synchronization timingreference comprises: determining that the synchronization source is aneNodeB when the root index corresponds to 25, 29, or
 34. 3. The firstwireless communication device of claim 1, wherein determining, by theprocessor, the synchronization timing reference comprises: determiningthat the synchronization source is a wireless communication device whenthe root index corresponds to a number different than 25, 29, and
 34. 4.The first wireless communication device of claim 1, wherein theprocessor is configured to: generate the synchronization signal for adirect communication based on a set for in-coverage when an eNodeB or awireless communication device synchronized with an eNodeB is selected asa transmission synchronization source for the determined synchronizationtiming reference; and generate the synchronization signal for a directcommunication based on a set for out-of-coverage when a wirelesscommunication device having a synchronization timing referenceindependent from an eNodeB is selected as the transmissionsynchronization source.
 5. The first wireless communication device ofclaim 4, wherein the set for in-coverage and the set for out-of-coveragecorrespond to different root indexes, which respectively correspond tonumbers different than 25, 29, and
 34. 6. The first wirelesscommunication device of claim 5, wherein transmitting, by thetransmitter, the synchronization signal for a direct communicationcomprises: generating a primary synchronization signal associated with aroot index corresponding to a number different than 25, 29, and 34;generating a secondary synchronization signal based on one of 168identities corresponding to the set for in-coverage or one of 168identities corresponding to the set for out-of-coverage; andtransmitting the primary synchronization signal and transmitting thesecondary synchronization signal.
 7. The first wireless communicationdevice of claim 1, wherein the processor is configured to: determinethat the first wireless communication device is an independentsynchronization source when the first wireless communication device doesnot determine a synchronization timing reference based on a receivedsynchronization signal.
 8. The first wireless communication device ofclaim 7, wherein the transmitter is configured to transmit asynchronization signal determined based on a set for out-of-coverage,when the first wireless communication device serves as an independentsynchronization source.
 9. A first wireless communication devicecomprising: a receiver to receive synchronization signals transmittedfrom different synchronization sources, respectively; a processor to:prioritize the different synchronization sources based on categories ofthe different synchronization sources, the categories comprising anevolved NodeB (eNodeB), a wireless communication device synchronizedwith an eNodeB, and a wireless communication device having asynchronization timing reference independent from an eNodeB; determine areference synchronization source for the first wireless communicationdevice among the different synchronization sources; synchronize with thereference synchronization source based on a synchronization timingreference associated with the reference synchronization source;determine a root index based on a primary synchronization signalreceived from the respective synchronization source; and determine,based on a secondary synchronization signal received from the respectivesynchronization source, one of 168 identities corresponding to a set forin-coverage or one of 168 identities corresponding to a set forout-of-coverage; and a transmitter to transmit, from the first wirelesscommunication device, a signal based on the synchronization.
 10. Thefirst wireless communication device of claim 9, wherein the prioritizingby the processor further comprises: prioritizing an eNodeB over awireless communication device synchronized with an eNodeB; andprioritizing a wireless communication device synchronized with an eNodeBover a wireless communication device having a synchronization timingreference independent from an eNodeB.
 11. The first wirelesscommunication device of claim 10, wherein the prioritizing by theprocessor further comprises: prioritizing a wireless communicationdevice located in a coverage of an eNodeB over a wireless communicationdevice located out of a coverage of an eNodeB.
 12. The first wirelesscommunication device of claim 10, wherein the processor is configuredto: determine a root index based on a synchronization signal receivedfrom the respective synchronization source; and determine a category ofthe respective synchronization source based on the root index.
 13. Thefirst wireless communication device of claim 9, wherein the processor isconfigured to: generate a primary synchronization signal based on acategory of the determined reference synchronization source, thegenerated primary synchronization signal relating to a root indexcorresponding to 26 or 37; and generate a secondary synchronizationsignal relating to one of 168 identities corresponding to a set forin-coverage or one of 168 identities corresponding to a set for out-of-coverage; and wherein the transmitter transmits the generated primarysynchronization signal and the generated secondary synchronizationsignal to a target wireless communication device for providing asynchronization opportunity.
 14. The first wireless communication deviceof claim 13, wherein: when the determined reference synchronizationsource corresponds to an eNodeB or a wireless communication devicesynchronized with an eNodeB, the generated secondary synchronizationsignal relates to one of 168 identities corresponding to the set forin-coverage.
 15. The first wireless communication device of claim 13,wherein: when the determined reference synchronization sourcecorresponds to a wireless communication device having a synchronizationtiming reference independent from an eNodeB, the generated secondarysynchronization signal relates to one of 168 identities corresponding tothe set for out-of-coverage.
 16. The first wireless communication deviceof claim 9, wherein the wireless communication device synchronized withan eNodeB comprises a wireless communication device directlysynchronized with an eNodeB and a wireless communication device havingan eNodeB as an original synchronization source with indirectsynchronization.
 17. A first wireless communication device comprising: areceiver to receive synchronization signals transmitted from differentsynchronization sources, respectively; a processor to: prioritize thedifferent synchronization sources based on categories of the differentsynchronization sources, the categories comprising an evolved NodeB(eNodeB), a wireless communication device synchronized with an eNodeB,and a wireless communication device having a synchronization timingreference independent from an eNodeB; determine a referencesynchronization source for the first wireless communication device amongthe different synchronization sources; synchronize with the referencesynchronization source based on a synchronization timing referenceassociated with the reference synchronization source; generate a primarysynchronization signal based on a category of the determined referencesynchronization source, the generated primary synchronization signalrelating to a root index corresponding to 2 or 37; and generate asecondary synchronization signal relating to one of 168 identitiescorresponding to a set for in-coverage or one of 168 identitiescorresponding to a set for out-of-coverage; and a transmitter totransmit, from the first wireless communication device, the primarysynchronization signal and the secondary synchronization signal to atarget wireless communication device for providing a synchronizationopportunity.
 18. The first wireless communication device of claim 17,wherein: when the determined reference synchronization sourcecorresponds to an eNodeB or a wireless communication device synchronizedwith an eNodeB, the generated secondary synchronization signal relatesto one of 168 identities corresponding to the set for in-coverage. 19.The first wireless communication device of claim 17, wherein: when thedetermined reference synchronization source corresponds to a wirelesscommunication device having a synchronization timing referenceindependent from an eNodeB, the generated secondary synchronizationsignal relates to one of 168 identities corresponding to the set forout-of-coverage.